npm vs pnpm
The default package manager vs the one that actually respects your disk space. Speed and correctness are not optional.
pnpm
pnpm is faster, uses less disk space, and enforces stricter dependency resolution. The only reason to stick with npm is if your team can't handle typing a different four letters.
The Default vs The Better
npm comes with Node.js. Everyone has it. Every tutorial uses it. It's the default.
pnpm is what you switch to after npm wastes 20GB of disk space duplicating the same packages across every project on your machine. The content-addressable store is not just clever engineering, it's table stakes.
Why pnpm Wins
Disk space. pnpm stores packages in a global content-addressable store and hard-links them into your project. 10 projects using React? One copy on disk. npm? 10 copies.
Speed. pnpm is consistently faster than npm. Not by a little. Install times can be 2-3x faster, especially on CI where cold caches hurt.
Strictness. pnpm creates a strict node_modules structure. You can't accidentally import packages you didn't declare as dependencies. npm lets you do this, which creates phantom dependencies that break in production.
Why npm Persists
Zero setup. It's already there. npm install works everywhere. No additional installation, no corepack setup, no team convincing.
Every tutorial, every README, every Stack Overflow answer uses npm commands. The ecosystem defaults to npm. Fighting that is friction.
npm has also gotten better. npm 10+ is significantly faster than older versions. The gap is narrowing, even if pnpm still leads.
The Migration Reality
Switching from npm to pnpm takes about 5 minutes: delete node_modules, delete package-lock.json, run pnpm import or pnpm install. Done.
The hard part is getting your team to switch. And your CI. And your deploy scripts. And that one person who insists npm is fine.
Quick Comparison
| Factor | npm | pnpm |
|---|---|---|
| Install Speed | Moderate | 2-3x faster |
| Disk Usage | Duplicates everything | Content-addressable store |
| Strictness | Hoists everything | Strict by default |
| Monorepo Support | Workspaces (basic) | Workspaces (excellent) |
| Setup Required | None (bundled) | Install separately |
| Ecosystem Compat | Universal | 99% compatible |
| Lockfile | package-lock.json | pnpm-lock.yaml |
| CI Performance | Slow without cache | Fast always |
The Verdict
Use npm if: You're working on a solo project, following a tutorial, or your organization mandates it. It works. It's fine.
Use pnpm if: You care about speed, disk space, or correctness. Monorepos, CI pipelines, teams, or anyone who has more than 3 projects on their machine.
Consider: Also look at Bun, which bundles its own package manager and is even faster. But pnpm is the safe, mature choice.
pnpm is faster, uses less disk space, and enforces stricter dependency resolution. The only reason to stick with npm is if your team can't handle typing a different four letters.
Related Comparisons
Disagree? nice@nicepick.dev