Monorepo Disk Bloat and How pnpm's Content-Addressable Store Fixes It
pnpm stores packages once in a global content-addressable store and hardlinks them into workspaces, eliminating monorepo disk duplication—if your tools handle symlinks.
Loading…
ReadMeFeed / Community knowledge
#node-modules
Real questions. Useful conversations. Find the people who know your stack.
pnpmDecision Guide: Yarn PnP vs Classic Install for Monorepos
Learn how to decide between Yarn PnP and classic node_modules installs in a monorepo, compare trade‑offs, and verify the chosen layout with concrete commands.
yarnSolving the Dual Package Hazard with npm peerDependencies
Stop duplicating core frameworks in your node_modules. Learn how to use npm peerDependencies and peerDependenciesMeta to prevent the dual package hazard in library development.
javascriptYarn Plug'n'Play: Trading node_modules for Speed Without Breaking Your Build
Yarn Plug'n'Play eliminates node_modules, but the speed gain comes with compatibility costs. Here is how to evaluate it safely.
Why pnpm Workspaces Stopped My Monorepo From Eating the Disk
pnpm workspaces store every dependency once in a content-addressable store and link it into each package, ending the monorepo habit of keeping ten copies of lodash. Here's how it works, a concrete setup, and the flat-tree trade-off.
Diagnosing 'Module Not Found' Errors in pnpm's Strict Dependency Tree
Learn how to diagnose and fix 'Module Not Found' errors in pnpm caused by strict dependency resolution and phantom dependencies, including when to use shamefully-hoist.
Resolving 'Module Not Found' Errors in pnpm's Non-Flat node_modules
Learn how to diagnose and fix 'Module not found' errors caused by pnpm's non-flat node_modules structure and how to handle phantom dependencies.
pnpm's isolated node_modules as a dependency hygiene check
pnpm's symlink-based node_modules makes phantom dependencies fail fast. This post explains the isolated layout, how to verify it locally, and the tooling trade-offs of strict resolution.
How pnpm's Store and Symlinked node_modules Work in Practice
pnpm stores each package version once in a global content-addressable store and builds node_modules from hard links and symlinks, saving disk space and blocking phantom dependencies by default.