Estimate node_modules size and the saving from a stricter package manager.
Flat dependency trees duplicate every package into every project, so disk usage scales with project count. A content-addressable store keeps one copy and links to it, which typically saves most of the space when projects share dependencies. File count matters as much as size, because tens of thousands of small files slow filesystem operations and backups disproportionately.
Node Modules Size
Flat trees duplicate packages per project; a content store keeps one copy and links to it
Flat trees duplicate packages per project; a content store keeps one copy and links to it Flat dependency trees duplicate every package into every project, so disk usage scales with project count. A content-addressable store keeps one copy and links to it, which typically saves most of the space when projects share dependencies.
File count matters as much as size, because tens of thousands of small files slow filesystem operations and backups disproportionately.
This calculator takes 5 inputs: Packages installed, Average package size, Projects on the machine, Share of packages common across projects, Package manager. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.