The official tutorial at https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager https://nodejs.org/en/learn/getting-started/an-i

The official tutorial at https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager https://nodejs.org/en/learn/getting-started/an-introduction-... says to use `npm install` and makes no mention of `npm ci` at all. Further, the name of the command (though not the clean-install alias) shows that it was tacked on top of a fundamentally broken base. > That's basically a crap shoot because even if you specifically pin the versions of all your dependencies, chances are that at least some of your dependencies did not have the good sense to do the same for their dependencies. As I mentioned in my first comment, I don't really want my dependencies to pin their dependencies. I want them to specify a range they work with to minimize the number of redundant copies of common transitive dependencies.