Install deno with Homebrew, apk, chocolatey, MacPorts, Nix, pacman, scoop, winget, zypper, apt, dnf

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• deno
• dx

Project history

The Deno repository was created in May 2018. The official Deno 1.0 announcement framed the project as a new runtime for JavaScript and TypeScript outside the browser, influenced by lessons from Node.js and designed around browser-compatible APIs, explicit permissions, first-class TypeScript, promises, Rust, and V8.

Deno 1.0 shipped in May 2020 as the stable CLI. The runtime deliberately bundled common developer tooling so users could run, test, format, lint, and document code without assembling a separate Node-style toolchain.

Deno 2, announced in October 2024, marked a shift from rejecting much of the Node ecosystem to supporting Node.js and npm compatibility. The Deno team described that release as combining Deno's original simplicity and security goals with package.json, node_modules, workspaces, npm specifiers, and private npm registries.

Adoption history

Early Deno adoption centered on developers who wanted browser-like module loading, TypeScript without a separate compiler setup, and a permission model for command-line scripts. Its official docs still present the tool as a secure-by-default runtime with a built-in formatter, linter, test runner, benchmarker, and package workflow.

After Deno 2, adoption broadened toward existing Node projects because Deno could run in repositories with package.json and node_modules while keeping Deno's own tooling and permission model. The release feed shows continued active releases, including Deno 2.9.0 in June 2026.

How it is used

Deno is used as a CLI runtime for scripts, services, tests, local tools, web servers, and TypeScript projects. The getting-started docs show deno init creating a project with deno.json, main.ts, and tests, then running TypeScript directly without a separate build step.

Package workflows can use URL imports, JSR packages, npm: specifiers, deno.json, or package.json depending on the project. Deno 2 also supports private npm registry configuration through .npmrc, which aligns it with enterprise Node package workflows.

Why package nerds care

Deno is package-nerd catnip because it challenges the usual JavaScript runtime/package-manager split. One executable brings together runtime, installer, formatter, linter, test runner, task runner, dependency management, and docs.

Its history also tracks a major ecosystem lesson: clean-slate runtimes are attractive, but compatibility wins adoption. Deno 2's Node and npm support made the package story less ideologically pure and much more operationally useful.

Timeline

• 2018: The denoland/deno repository is created on GitHub.
• 2020: Deno 1.0 is announced as the first stable CLI release.
• 2024: Deno 2 is announced with Node.js and npm compatibility.
• 2026: Deno 2.9.0 is published on GitHub releases.

Related projects

• Node.js is the historical reference point and compatibility target for Deno 2.
• V8 and Rust are core implementation technologies discussed in the Deno 1.0 announcement.
• JSR is Deno's TypeScript-first package registry companion.
• Fresh and Deno Deploy are related Deno ecosystem projects from Deno Land.

Sources

• https://github.com/denoland/deno
• https://api.github.com/repos/denoland/deno
• https://api.github.com/repos/denoland/deno/releases
• https://deno.com/blog/v1
• https://deno.com/blog/v2.0
• https://docs.deno.com/runtime/