News for hackers. Stuff that matters.
Re:Changes to Npm's unpublish policy by jerf on Tuesday March 29, 2016 @03:04PM (#11383976)
"With npm every dependency gets it's own tree of dependencies, so there's tons of duplication."

That sounds like the missing bit of info.

If that is the primary problem, then the good news is that git actually ought to be able to re-de-dupe that stuff back down; checking it into git may not be as catastrophic as you'd initially think.

Re:Changes to Npm's unpublish policy by tlrobinson on Tuesday March 29, 2016 @04:07PM (#11384442)
Good point. If I add my node_modules to a new git repo it ends up being about 65MB, which is better, but still significant, and I imagine the overhead of tracking an additional 100,000+ files is non-trivial.
Re:Changes to Npm's unpublish policy by etblg on Tuesday March 29, 2016 @10:23PM (#11386542)
That also shouldn't be true in the latest npm, which uses a global node_modules and a bit of trickery for different versions of the same library, instead of recursive node_modules.