3 ms·
It may look brittle to a newcomer, but it in my actual experience it is way less brittle than Python, Java or C++ ecosystems. The size is mostly due to packages
by incrudible 5y ago
It may look brittle to a newcomer, but it in my actual experience it is way less brittle than Python, Java or C++ ecosystems. The size is mostly due to packages shipping three different module types in multiple flavors.
I am upset about having node_modules in my source tree, however. A global package cache should be a thing.
- Sankozi 5y agoI have never had to decide which exact Maven version (Java build tool) to use in team and on CI server when developing in Java. Most of the times you can safely use any version of Java that is higher than currently required in project. My team wasted a lot of time finding version of node/npm/yarn that works on CI and on all developer machines. Purging whole node_modules and installing everything again used to be weekly occurrence. It is much better now but poor design of JS ecosystem still makes me nervous when I have to update node, npm or bigger dependency.
- incrudible 5y agoYMMV. I'm not saying nothing in the ecosystem ever breaks. I'm saying that despite it being unstable, it is much more resilient than it is brittle. It does look crazy at first glance, you have to experience it to believe it.
- julian37 5y agoYou can have a global package cache today with Berry (Yarn 2/3) although there are still a few tools (say, serverless package) that break without node_modules where they expect it to be. It's gotten a lot better though over the last few months.