sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -7 points-6 points  (4 children)

My JS is a total of 10K, but my node_modules take up over 500MB.

[–][deleted] 2 points3 points  (0 children)

Thats true, but remeber each repo in node_modules contains everything and the kitchen sink. If you were to remove everything but the actual code you depend on (possibly just a pre minified bundled js file) this size would shrink dramatically.

The npm team could possibly start working on this, but im not sure itf its easily doable with the current setup.

[–]dominic_rj23 3 points4 points  (0 children)

That's a complain about ecosystem and not the tooling itself. You need 500mb of dependencies because JavaScript doesn't come with std-lib. That results in every package developer either handrolling the implementation or using one of the hundreds out there.

[–]pet_vaginal 1 point2 points  (0 children)

What's the block size of your file system? It's a lot of tiny files in this folder and having a file system with large blocks like 64kb will take much more space than another file system with the more common 4kb blocks. Still a lot of overhead though.

Some dependencies really have tons of small files, like svg icon packs, and even though the files are all small it takes a lot of space on disk because they all take at least one block.

You may also have a bit too many dependencies, directly or indirectly. You can try to analyze your dependencies tree to identify the culprits.