Deno (software)

Deno

Logo used since 2024
Original author(s)	Ryan Dahl
Developer(s)	Deno Land Inc[1] and contributors
Initial release	May 13, 2018; 6 years ago (2018-05-13)[2]
Stable release	2.2.11[3]  / 18 April 2025; 14 days ago (18 April 2025)
Repository	github.com/denoland/deno
Written in	TypeScript, JavaScript, Rust, C++ (V8 bindings)
Operating system	Linux, macOS, Microsoft Windows
Type	Runtime environment
License	MIT License[4]
Website	deno.com

Deno (/diːnoʊ/^[5]) is a runtime for JavaScript, TypeScript, and WebAssembly that is based on the V8 JavaScript engine and the Rust programming language. Deno was co-created by Ryan Dahl, the creator of Node.js^[6] and Bert Belder.^[7]

Deno explicitly takes on the role of both runtime and package manager within a single executable, rather than requiring a separate package-management program.^[5][8]

Deno was announced at JSConf EU 2018 by Ryan Dahl in his talk "10 Things I Regret About Node.js".^[9] In his talk, Dahl mentioned his regrets about the initial design decisions with Node.js, focusing on his choices of not using promises in API design, usage of the legacy build system GYP, node_modules and package.json, leaving out file extensions, magical module resolution with index.js and breaking the sandboxed environment of V8.^[10] He eventually presented the prototype of Deno, aiming to achieve system call bindings through message passing with serialization tools such as Protocol Buffers, and to provide command line flags for access control.

Deno was initially written in Go and used Protocol Buffers for serialization between privileged (Go, with system call access) and unprivileged (V8) sides.^[11] However, Go was soon replaced with Rust due to concerns of double runtime and garbage collection pressure.^[12] Tokio was introduced in place of libuv as the asynchronous event-driven platform,^[13] and FlatBuffers was adopted for faster, "zero-copy" serialization and deserialization^[14] but later in August 2019, FlatBuffers was removed^[15] after publishing benchmarks that measured a significant overhead of serialization in April 2019.^[16]

A standard library, modeled after Go's standard library, was created in November 2018 to provide extensive tools and utilities, partially solving Node.js' dependency tree explosion problem.^[17]

The official Deno 1.0 was released on May 13, 2020.^[18]

Deno Deploy, inspired by Cloudflare Workers,^[19] was released on June 23, 2021.^[20] Announced May 4, 2022 Beta 4 improved the dashboard and added billing functionality.^[21]

Deno Fresh 1.0 was announced June 28, 2022.^[22] It features a new full stack web framework for Deno that by default sends zero JavaScript to the client. The framework has no build step which allows for an order of magnitude improvements in deployment times. Version 1.1 was released September 8, 2022.^[23]

Deno SaaSKit beta was announced April 4, 2023.^[24] It is an open-source, modern SaaS template built with Fresh and Deno.

Deno 2 was released October 9, 2024.^[25] It primarily brings Node.js compatibility improvements and removes deprecated features.

Deno aims to be a productive and secure scripting environment for the modern programmer.^[5] Similar to Node.js, Deno emphasizes event-driven architecture, providing a set of non-blocking core I/O utilities, along with their blocking versions. Deno could be used to create web servers, perform scientific computations, etc. Deno is open source software under the MIT License.^[26]

Deno and Node.js are both runtimes built on the V8 JavaScript engine developed by the Chromium Project, the engine used for Chromium and Google Chrome web browsers. They both have internal event loops and provide command-line interfaces for running scripts and a wide range of system utilities.

Deno mainly deviates from Node.js in the following aspects:^[5]

1. Supports only ES Modules like browsers where Node.js supports both ES Modules and CommonJS. CommonJS support in Deno is possible by using a compatibility layer.^[27][28]
2. Supports URLs for loading local or remote dependencies, similar to browsers, and uses module specifiers like npm: and node: to import NPM or polyfill Node.JS modules. Node.js supports both URLs^[29] and modules.
3. Does not require a package manager for resource fetching, thus no need for a registry like npm.^[30]
4. Supports TypeScript out of the box,^[31] using a snapshotted TypeScript compiler or the swc compiler^[32] with caching mechanisms.
5. Aims for better compatibility with browsers with a wide range of Web APIs.
6. Restricts file system and network access by default in order to run sandboxed code.
7. Supports a single API to utilize promises, ES6 and TypeScript features whereas Node.js supports both promise and callback APIs.
8. Minimizes core API size, while providing a large standard library with no external dependencies.
9. Uses message passing channels for invoking privileged system APIs and using bindings.

On March 29, 2021, Deno Land Inc was announced, with backing in millions of dollars from Shasta Ventures, Mozilla Corporation and a few others. It was established to further the development of Deno and provide a commercial offering to users.^[1]

A year on, Deno announced a further $21 million in Series A funding led by Sequoia Capital.^[33]

This article may require cleanup to meet Wikipedia's quality standards. The specific problem is: Reads like a software tutorial. Some code examples may be useful to illustrate aspects of the framework, but they should be selected for the purpose of providing context to an encyclopedia article on the software. Please help improve this article if you can. (July 2023) (Learn how and when to remove this message)

Global Deno namespaces expose APIs that are not available in the browser.

An implementation of the Unix cat program: [1]

/**  * cat.ts  */ for (const filename of Deno.args) {   const file = await Deno.open(filename);   await file.readable.pipeTo(Deno.stdout.writable, { preventClose: true }); } 

A simple Web server: [2]

Deno.serve((req) => new Response("hello world")); 

Deno automatically downloads and caches the remote standard library files when the script is run, and then compiles the code.

Similarly, it can run a standard library script (such as a file server) directly without explicitly downloading, by providing the URL as the input filename (-A turns on all permissions):

$ deno run -A https://deno.land/std/http/file_server.ts Download https://deno.land/std/http/file_server.ts Compile https://deno.land/std/http/file_server.ts ... HTTP server listening on http://0.0.0.0:4500/ 

• Official website