Deno 2 Released: Backwards Compatible with Node.js and npm

What happened

Deno 2 was released on October 9, 2024, according to the official announcement on the Deno blog, authored by the Deno team including creator Ryan Dahl. Where Deno 1 established a modern, all-in-one, zero-config toolchain for JavaScript and TypeScript, the second major version was focused on using Deno at scale, meaning seamless interoperability with legacy JavaScript infrastructure without sacrificing Deno's simplicity, security and batteries-included nature.

Node.js and npm compatibility

The headline of Deno 2 was robust backwards compatibility with Node.js and npm. Deno 2 understands package.json, the node_modules folder and even npm workspaces, so it can run existing Node applications and let teams incrementally adopt parts of Deno's toolchain. Developers can import npm packages directly using npm: specifiers, giving access to over two million npm modules, including complex packages such as gRPC, Prisma and Polars, and even Node-API native addons.

A built-in package manager

Deno 2 turned Deno into a package manager with three new subcommands: deno install to install dependencies at high speed, and deno add and deno remove to manage packages in package.json or deno.json. The announcement said deno install is 15% faster than npm with a cold cache and 90% faster with a hot cache. Deno 2 also supports private npm registries via an .npmrc file and adds workspaces and monorepo support.

Stable standard library, JSR and LTS

The release stabilised the Deno Standard Library, a set of audited utility modules built over more than four years and published on JSR, the modern TypeScript-native JavaScript registry Deno introduced earlier in the year. Deno 2 also introduced a Long Term Support release channel starting with Deno 2.1, back-porting critical bug fixes for six months, and improved existing tools such as deno fmt, deno lint, deno test and deno compile.

Why it mattered

Deno 2 addressed the biggest practical barrier to adopting Deno: the need to leave the vast Node and npm ecosystem behind. By becoming compatible with Node and npm while keeping native TypeScript, web-standard APIs and secure-by-default execution, Deno 2 positioned itself as a runtime teams could adopt incrementally in real, large-scale projects.

Related on Skillo

See also: Bun 1.0 and the all-in-one toolkit.

Sources

• Announcing Deno 2 (official Deno blog)

Published date reflects the original event date (2024-10-09). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.