Bun is not a package manager in the traditional sense. It is a complete JavaScript and TypeScript toolkit delivered as a single executable, combining a runtime, a package manager, a bundler, and a test runner into one cohesive tool . The package manager is one component of this toolkit, but it is inseparable from the…
npm is the package manager for the Node JavaScript platform. Its job is to put modules in place so that Node.js can find them, and to manage the dependency conflicts that arise when different packages require different versions of the same library . The name originally stood for “Node Package Manager,” and it refers to…
Every JavaScript package manager before pnpm solved the same problem in the same way: download packages, copy them into a node_modules folder, and repeat for every project. pnpm discards the copying entirely. It stores every file of every package exactly once on your disk in a global content-addressable store, then constructs a node_modules directory out…
The JavaScript ecosystem has never had a single package manager. For years, npm was the default—it shipped with Node.js, and it worked. But in 2016, Yarn arrived with a promise of speed, determinism, and better dependency management. Nearly a decade later, the landscape is more complicated: Yarn has evolved through multiple major versions, npm has…
Bun is distributed as a single, dependency-free executable. There is no runtime environment to configure, no virtual machine to install, and no package manager to bootstrap. The installation is one command, and the resulting binary contains everything: the runtime, the package manager, the bundler, and the test runner. Managing versions is equally direct: bun upgrade…
Node.js and npm are installed together, but they are versioned separately. Node.js ships with a specific npm version bundled into each release—Node.js 24.19.0 includes npm 11.17.0, for example—and npm releases new versions more frequently than Node.js does . This means the npm you have is not necessarily the latest npm, even if your Node.js is…
The conventional wisdom around pnpm installation has shifted significantly. Corepack, once the recommended path, is now considered outdated by the pnpm maintainers themselves, with the standalone script emerging as the preferred method. This chapter covers both approaches, the reasons for the shift, and the version-pinning mechanism that makes pnpm installations reproducible across machines and CI…
Installing Yarn used to mean a single global command. That era is over. Modern Yarn—versions 2, 3, and 4, collectively called “Berry”—is designed to be installed per-project, not globally. The tool that makes this possible is Corepack, a Node.js utility that intercepts yarn commands and routes them to the exact version declared in your project’s…
Bun’s project initialization is designed to eliminate the configuration burden that Node.js projects typically carry. Running bun init generates a complete, working project with sensible defaults, and it integrates with package.json in ways that differ from npm and Yarn: it writes a typecheck script, it understands workspaces natively, and it defaults to treating package scripts…
Every Node.js project begins with a package.json file. It is the manifest that records the project’s name, its version, its scripts, and the dependencies it needs. Creating that file by hand is possible but error-prone: a missing name, a version that does not follow semantic versioning, or a typo in the scripts key produces a…