What makes pnpm performant
summary
Argues that using an isolated node_modules layout with symlinked packages plus a content-addressable store makes installations both space- and time-efficient: identical files across projects are hard-linked once, saving “10–30 GB” when you have ~10–20 projects, and downloads grow “three times” year-over-year. Claims a different algorithm that does concurrent resolve/fetch/write yields multix speedups versus npm/yarn. Notes monorepo correctness benefits, symlink compatibility issues (react-native) and a hoisted fallback, plus a pnpm command to install Node versions globally.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:51Evolution of package managers
- 6:14pnpm module structure
- 11:23Advantages of isolated node_modules
- 13:10Disk space efficiency
- 16:45Installation speed
- 19:39Node.js version management
- 20:48pnpm features overview
related talks
05mRevisiting Node modules
31mKat Marchán - SeattleJS Conference 2017
30mnpm 5: Bringing Package Management to the Future
39mThe Structure of Node.JS Applications
31mnpm: paster, presenter, futurer
19mNpm, Yarn — What If the Truth Lies Elsewhere
28mHow npm Works
25mLevelling up Monorepos with npm Workspaces