Change8

Deno

Backend & Infra

A modern runtime for JavaScript and TypeScript.

Latest: v2.9.625 releases4 common errorsView on GitHub

Release History

View all versions →
v2.9.672 fixes3 features
Aug 27, 2026

This release includes numerous bug fixes across various modules, including desktop, fetch, http, node, npm, and web. It also introduces performance improvements in the core and web modules.

v2.9.554 fixes4 features
Aug 6, 2026

This release introduces several new features, including unscoped package aliasing and a QuickJS backend, alongside numerous bug fixes across various modules like bundle, cjs, cli, core, crypto, and more. Performance has also been improved in several areas.

v2.9.457 fixes4 features
Jul 23, 2026

This release introduces new features like HMR for React Router and enhanced buffer manipulation in Node.js extensions, alongside numerous bug fixes across various modules including desktop, core, and npm operations.

v2.9.331 fixes4 features
Jul 15, 2026

This release introduces new CLI flags for dependency management, adds support for a new compilation target, and includes numerous bug fixes and performance improvements across various modules including fetch, node, and web APIs.

v2.9.254 fixes10 features
Jul 8, 2026

This release introduces several new features across desktop, extensions, and Node compatibility, alongside numerous performance improvements, especially within Web Streams and NPM handling. Numerous bug fixes address stability, coverage reporting, and installation reliability.

v2.9.143 fixes3 features
Jul 1, 2026

This release introduces desktop-specific features like type-checking flags and deep-link registration, alongside numerous fixes across bundling, caching, desktop environment, Node.js compatibility, and npm handling.

v2.9.051 fixes58 features
Jun 25, 2026

Deno 2.9.0 introduces significant CLI enhancements with new subcommands like `deno watch` and improved package manager integration for lockfile seeding. This release also stabilizes several features, including bare node built-in resolution and the "links" field in deno.json, alongside numerous fixes across crypto, fetch, and Node.js compatibility layers.

v2.8.383 fixes26 features
Jun 11, 2026

This release introduces numerous features across the CLI, LSP, and various extensions, including support for watch mode in compile, enhanced telemetry configuration, and fixes for Node.js compatibility and crypto operations.

v2.8.294 fixes14 features
Jun 3, 2026

This release introduces significant new cryptographic features, enhances the `deno compile` command with bundling improvements and a new --minify flag, and brings numerous fixes across Node.js compatibility, LSP, and Jupyter kernel support.

v2.8.134 fixes1 feature
May 27, 2026

This release focuses heavily on bug fixes across Node.js compatibility, bundling, and runtime stability. Key improvements include better handling of npm specifiers and various fixes in the node extension for TLS, file system, and utility functions.

v2.8.047 fixes61 features
May 22, 2026

Release 2.8.0 introduces numerous features across CLI commands, Node.js compatibility (especially around inspector events and module loading), and core runtime enhancements. Key additions include `deno audit fix`, `--watch` for `deno check`, and extensive stabilization of Node APIs.

v2.7.1491 fixes2 features
Apr 28, 2026

This release focuses heavily on Node.js compatibility, bringing numerous fixes and alignments across modules like fs, net, http2, and crypto. New features include fs.Utf8Stream and support for delta updates via bsdiff patches.

v2.7.1329 fixes3 features
Apr 22, 2026

This release introduces significant enhancements to Node.js compatibility, including rewriting node:http with llhttp and implementing the node:repl module. Numerous bug fixes address issues across HTTP/2, TLS, file system operations, and runtime stability.

v2.7.1227 fixes4 features
Apr 9, 2026

This release introduces several native extensions for Node compatibility, including file system streams, HTTP parsing, and TLS handling. Numerous bug fixes address stability, memory leaks, and permission checks across core, node, and webgpu modules.

v2.7.112 fixes1 feature
Apr 1, 2026

This release introduces support for alpha and beta release channels and includes fixes for file watching events and graceful shutdown timeouts.

v2.7.1018 fixes1 feature
Mar 31, 2026

This patch introduces new configuration options for compilation and resolves numerous bugs across Node.js extensions, LSP, package resolution, and security compatibility.

v2.7.910 fixes
Mar 27, 2026

This maintenance release focuses on numerous bug fixes across the CLI, compilation, Node.js extension, and HTTP extensions, alongside performance improvements in metrics handling.

v2.7.852 fixes6 features
Mar 25, 2026

This release introduces significant improvements to Node.js compatibility, including fixes for child_process, fs, and various internal APIs. It also adds new features like P-521 cryptography support and OpenTelemetry console exporting.

v2.7.711 fixes
Mar 19, 2026

This release focuses primarily on bug fixes across the core and Node.js extension, including improved compatibility, security enhancements, and stability improvements.

v2.7.665 fixes7 features
Mar 18, 2026

This release introduces performance improvements across V8 string conversion, NAPI async work, and various web/node extensions. It also brings numerous bug fixes, particularly enhancing Node.js compatibility and fixing panics in core functionality.

v2.7.538 fixes6 features
Mar 11, 2026

This release introduces significant enhancements to coverage reporting, Node.js compatibility (especially around crypto and HTTP/2), and performance improvements across the npm subsystem. Numerous bug fixes address stability and correctness across various core and extension modules.

v2.7.46 fixes
Mar 5, 2026

Version 2.7.4 focuses primarily on bug fixes across core, deployment, and node extensions, alongside performance improvements for npm binary startup.

v2.7.36 fixes
Mar 4, 2026

This patch release focuses on stability and performance improvements across deployment, Node.js extensions, and npm handling, fixing several regressions and integration issues.

v2.7.243 fixes3 features
Mar 3, 2026

This release brings significant stability improvements across crypto, installation, and Node.js compatibility, including an upgrade to V8 14.6 and fixes for coverage reporting and environment variable loading.

v2.7.11 fix
Feb 25, 2026

This is a maintenance release that specifically fixes an issue where `deno --version` produced incorrect output in the previous v2.7.0 release.

Common Errors

GetLastError2 reports

The GetLastError error in Deno often arises from issues loading native addons, such as incorrect library paths or missing dependencies. To fix this, ensure the addon's DLL file is accessible and all its dependencies are installed correctly on your system, then verify the addon path in your Deno script is accurate.

NodeSystemError2 reports

NodeSystemError in Deno often arises from Deno's compatibility layer attempting to use Node.js APIs (like `tty`) in environments where they're unavailable or improperly configured, such as a broken terminal or during automated script execution. To resolve this, either avoid using Node.js compatibility APIs if possible or ensure the environment is properly set up to support `tty` operations. For instance, verify a valid terminal is attached or stub out `tty` functions if running in a non-interactive environment.

NotSupportedError2 reports

This error typically occurs in deno. Check the example issues for common solutions.

DataCloneError1 report

DataCloneError in Deno typically arises when attempting to pass non-cloneable objects (like DOM nodes, functions, or ReadableStreams) across the Deno isolate boundary, such as when using `postMessage` or Workers. To resolve this, ensure you only pass cloneable data structures (plain objects, arrays, primitive values) or serialize/deserialize the non-cloneable data into a transferable format (e.g., using `structuredClone` for complex objects or manually converting Streams to ArrayBuffers). If using `postMessage`, leverage the `transfer` option to efficiently move ownership of ArrayBuffer data instead of cloning it.

Related Backend & Infra Packages

Subscribe to Updates

Get notified when new versions are released

RSS Feed