Deno has some momentum, with 4.1 million downloads on GitHub and 250k month-to-month energetic customers based on the submit, however its largest adoption blocker is the dominance of the Node and npm ecosystem, which is embedded within the software program growth course of for a lot of builders. Dahl and Bonder now say that “we’ve been engaged on some updates that can enable Deno to simply import npm packages and make 80-90 p.c of npm packages work in Deno inside the subsequent three month.”
Deno 1.0 was launched in 2020, and Dahl said that it was an effort to repair “design errors in Node” with a brand new and higher runtime. Options embody native TypeScript and WebAssembly assist, and net platform requirements together with use of ES (EcmaScript) modules, whereas Node.js has the extra legacy of CommonJS modules.
Deno doesn’t presently use the npm bundle supervisor although, or any bundle supervisor. “In Deno there isn’t any idea of a bundle supervisor as exterior modules are imported instantly into native modules,” the docs explain.
The Deno neighborhood has reacted positively to the bulletins, with npm compatibility the massive attraction, although one developer on Deno’s Discord discussion board requested “The assist of 80-90% of npm pkg in deno shall be nice however how we all know if pkg x shall be supported or not?”
One other developer, on Hacker Information, said that “npm compatibility is big for Deno. It’s mainly the one main disadvantage to Deno.”
That stated, cementing the dominance of npm is a possible draw back for some. “Npm is the primary factor I dislike about Node … I hope compatibility is a characteristic meant for alleviating transitions, not one thing the overall person base must be embracing,” opined one other dev.