pnpm – a Fast, Disk Space Efficient Package Manager for JavaScript
summary
Claims concrete outcomes: isolated node_modules implemented with per-package relocations and symlinks prevents accidental undeclared dependency access; content-addressable store with hard links reuses identical files across projects to cut disk usage; pipelined per-package install stages make installs measurably faster than npm/Yarn by overlapping resolve fetch and write; monorepo workspace links only direct deps and offers a hoisted linker fallback for broken tooling; pnpm ships as an executable and can install and switch Node.js versions.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:13JavaScript package managers
- 3:22pnpm advantages
- 5:50Isolated node_modules
- 9:06Live demo: pnpm install
- 11:04pnpm monorepo support
- 13:55npm vs pnpm approach
- 15:02Disk space efficiency
- 18:15Content-addressable storage
- 18:36Why pnpm is faster
- 20:22Node.js version management
- 21:04Choosing package manager
- 21:46Conclusion and resources
related talks
30mnpm 5: Bringing Package Management to the Future
19mNpm, Yarn — What If the Truth Lies Elsewhere
41mThe Future of JavaScript Package Management
27mnpm i g @next and beyond: Building the future of package management
31mWhat everybody should know about npm
32mThe JavaScript coders guide to getting more from GitHub and NPM
41mnpm and the Future of JavaScript
41mnpm and the Future of JavaScript