pnpm Catalogs — A New Tool to Manage Dependencies in monorepos
summary
pnpm introduces catalog: as a new protocol that centralizes dependency versions so a monorepo keeps a single declared version instead of accidentally installing multiple ones (example given: Vue 3.3.0 vs 3.3.4). Developers add a catalog object to pnpm-workspace.yaml and subsequent pnpm add calls reuse that constant, preventing runtime breaks and TypeScript errors, reducing package.json and pnpm-lock.yaml conflicts. RFC is ratified and implementation is expected in the next few months.
AI-written summary · about
chapters (6)
- 0:00Introduction to pnpm
- 2:11The monorepo challenge
- 4:09Debugging version conflicts
- 6:42Introducing pnpm catalogs
- 8:30Benefits and implementation
- 10:21Conclusion and recap
related talks
45mNext Gen Package Management
41mHandling Monorepos Today
41mThe Future of JavaScript Package Management
32mThe JavaScript coders guide to getting more from GitHub and NPM
19mMonorepos: Any Size Fits All
11mWhat's Next for npm
28mPanel - Package Managers: Before and After npm
46mExploring the power of monorepos: When and why to use them