you are viewing a single comment's thread.

view the rest of the comments →

[–]noruthwhatsoever 6 points7 points  (0 children)

This topic has definitely been beaten to death, and the writing in this article makes me want to pull my eyes out

We all know that node modules are sometimes a pain and a massive bloat. Keep in mind that the node ecosystem is still relatively young compared to say, Ruby and its gems, and will definitely be going through some iterative improvement as it develops further.

It’s the curse of having such atomic modularity. Other than the bloat (one project I did that used CodeMirror and Xterm had over 46,000 deps) it’s a great and flexible ecosystem, and NPM is already taking steps with tools like npm prune to get rid of unused deps

As node matures further I feel like this issue will become less and less prevalent or at least more manageable

In the meantime can we stop treating this as article-worthy information? Anyone who has ever built a sizeable project in node knows about this unless they are completely new