This is, arguably, the most controversial change that Deno has introduced into the JavaScript-for-the-back-end landscape: the lack of a package manager. Let’s be honest—this is not about them dropping support for NPM, which, if you don’t know about it, is the de facto package manager for Node.js. This is about them dropping the entire concept of a package manager altogether and letting back-end developers handle dependencies like browsers do.
Is this a good approach? Will it break the entire ecosystem and make the Deno community collapse? I’m not telling you now; you’ll have to read and see for yourself! ...
