Arborist module: How npm install REALLY works
summary
Explains exactly what npm does when running npm install: Arborist analyzes the project, builds an actual tree and an ideal tree, then plans and executes filesystem changes with fully atomic rollback support. Shows why npm 7 auto-installing peer deps (vs npm 6) creates version collisions with a concrete eslint vs Vue CLI example, and demonstrates Node’s module resolution rule of searching node_modules upward through parent folders. Includes the five-step Arborist pipeline and the practical fix: upgrade the peer or downgrade the installed package to resolve the conflict.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker intro
- 1:04Personal story and motivation
- 3:32Root cause analysis with Five Whys
- 4:16Understanding npm error arrows
- 6:01Types of npm dependencies
- 7:27Peer dependencies in npm 6 vs 7
- 8:52Dependency conflicts explained
- 10:19Dependency graph vs dependency tree
- 11:24Scale of npm ecosystem
- 12:49Node module resolution process
- 13:51Node module isolation in file system
- 15:13Introducing Arborist model
- 15:55How Arborist manages dependencies
- 17:40Arborist execution and rollback
- 19:05Solving the npm error
- 19:49Summary and key takeaways
related talks
27mnpm i g @next and beyond: Building the future of package management
30mWhat's Really Going on Inside Your Node_Modules Folder
11mWhat's Next for npm
19mWhat You’re Really Trusting When You Run npm install
17mWhat's New in
31mWhat's Going on Inside the Node_Modules Folder
44mYou Don't Know npm
31mWhat everybody should know about npm