This is a great read that can be applied to node.js very much. I&#x27;ve seen apps that include 10, maybe 20 dependencies but when you flatten out the full dependency tree? Thousands. It&#x27;s incredible and if one of those dependencies screws up semantic versioning or just screws up in general it can be a nightmare to debug and fix.<p>This is why every 1.0 product I work on I include every dependency that speeds up my development. In 2.0 the first things to do is prune all unnecessary dependencies and start minor rewrites when a dependency can be done in house (yeah yeah reinventing the wheel is a problem but most npm dependencies are small and many can be recreated internally without issue).<p>This is even more important if you&#x27;re creating a library &#x2F; module. My msngr.js library uses zero dependencies and yet can make http calls in node and the browser because it was easy to implement the minimal solution I needed without bringing in dependencies to support a single way of calling http.