npm vs pnpm vs yarn — pick pnpm

medium

Learn with your AI

Open this lesson in your favourite AI. It'll walk you through the why, explain the demo, and quiz you on the try-it list.

Open in Claude Open in ChatGPT

Why this matters

Three package managers, all working. npm is built into Node and 'just works' but is slow on large monorepos. yarn (especially v3+ Berry) is fast but has a flatter community. pnpm is the 2026 winner: it uses a content-addressed global store + symlinks so installs are 2-3× faster and disk-cheap, has the best workspace support, and is officially recommended by Vercel, Vite, etc. Pick pnpm for new projects unless your team has a specific reason otherwise.

Demo

npm, yarn, and pnpm solve the same problem — installing packages — but with meaningfully different strategies for deduplication and disk efficiency. npm uses a flat node_modules tree that can balloon to gigabytes in a large monorepo because each package gets its own copy of shared dependencies; pnpm uses a global content-addressable store and symlinks, meaning 100 projects can share one copy of React on disk. Measuring install time and disk footprint across all three on a real project gives you the empirical basis to make an informed choice rather than cargo-culting whatever your last project used.

Try it yourself

Install pnpm globally: corepack enable && corepack prepare pnpm@latest --activate.

Run pnpm install on the same project that previously used npm. Time both — pnpm should be 2-4× faster on warm cache.

Look at node_modules after pnpm install. Note it's mostly symlinks into ~/.local/share/pnpm/store — that's the magic.

Add a pnpm-workspace.yaml with packages: ["apps/*", "packages/*"]. Now you have a monorepo. We'll use this in M6.

Prompt your AI

Use these three in order. Each builds on the one before.

1. Basics & terminology

In one paragraph, explain why pnpm is faster than npm — the content-addressed store, symlinks, and parallel resolution.

2. Why it works (the mechanism)

Walk me through how pnpm's symlink layout in `node_modules` differs from npm's flat layout. Why doesn't this break Node's module resolution?

3. Advanced — application & what's next

On a monorepo with 50 packages, pnpm should win. But there's a known incompatibility class — packages that don't expect symlinks. What are the symptoms and how do I work around them?