I've seen some recently ponder why ppl make a big deal about many module deps. I'll give you a little tweet storm to illustrate why I do...
I thought the same and started opening PRs. Most got rejected. Authors said tests and docs should be included
-
-
Yeah, I definitely think that's part of the problem. Module authors don't see it as a bug, so low priority
-
most of the node projects I work on do separate devDependencies from prod ones.
-
problem is the files included. Not deps. Many modules include docs/tests/examples in tarball
-
Well that problem I was specifically talking about *was* deps. 3,947 of them. Due to bad includes
-
The per-dep overhead is definitely larger than the overhead of large deps. But in any case, same cause –
-
And that is, ppl publishing things without realising it. And the tools aren't helping them.
End of conversation
New conversation -
-
-
really npm needs a way to specify things that can be excludes from production builds
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.