> I don't like the `npm i` in node.js pulls hundreds of modules Because modules/packages routinely have dependencies. And their dependencies have dependencies.

> I don't like the `npm i` in node.js pulls hundreds of modules Because modules/packages routinely have dependencies. And their dependencies have dependencies. And... Deno changes nothing in that regard with one single exception: > a standard library that contains most commonly needed modules is the key ^ This is the bane of Javascript, yes. But this doesn't mean that having a standard library somehow prevents modules having multiple dependencies and subdependencies. > "you pull whatever you want freely now even over http URL", for security and stability reasons. - If you pull your deps from a random URL and that URL goes away, how do you solve that? - If your deps pull other subdeps from a random URL and that URL goes away, how do you solve that? - For security, how do you vet what your dependencies keep on pulling from random URLs? For node, the answer is: run your own registry, and don't load anything from outside. That's how many companies operate. How can this be solved with Deno?