Deno 2.7 sharpens Node.js compatibility and stabilizes Temporal

With Deno 2.7, the team releases an update that further advances both web standards and Node.js compatibility. The focus is on stabilizing the Temporal API and providing extended control over dependencies in package.json. Additionally, the release includes official builds for Windows on ARM, numerous Node.js fixes, and an upgrade to V8 14.5.

Temporal API now usable without flag

With Deno 2.7, the Temporal API leaves its experimental status. The previously required flag --unstable-temporal is removed. Deno thus follows the development in the V8 ecosystem: Since Chrome 144 (January 2026), the Temporal API will also be available by default; Deno is now catching up as part of the upgrade to V8 14.5.

An example from the announcement post is intended to clarify the innovation:

const today = Temporal.Now.plainDateISO();
const nextMonth = today.add({ months: 1 }); // immutable - today unchanged

const meeting = Temporal.ZonedDateTime.from(
  "2026-03-15T14:30[America/New_York]",
);
const inTokyo = meeting.withTimeZone("Asia/Tokyo"); // same instant

The Temporal API is intended to address the known weaknesses of the Date object and offers clearly defined types for points in time, dates, durations, and time zones. Developers thus receive more precise tools for complex date and time calculations – for example, for recurring appointments, international applications, or processing timestamps with time zone references.

For Deno projects, the stabilization primarily means planning security: applications can use the Temporal API productively without having to expect API changes. At the same time, interoperability with modern browser environments is expected to improve.

JavaScript conference by heise: enterJS 2026

Tools and trends in the JavaScript world: The enterJS 2026 will take place on June 16 and 17 in Mannheim. The program revolves around JavaScript and TypeScript, frameworks, tools and libraries, security, UX, and more. Early bird tickets are available in the online ticket shop.

Fine-grained control with package.json overrides

A second central feature is the support for the overrides field in package.json. Deno is thus further expanding its support for Node.js projects. The goal, according to the announcement post, remains to make existing Node.js applications runnable under Deno with as few adjustments as possible.

With overrides, versions of transitive dependencies can be specifically overwritten. Developers can thus, for example, globally pin a vulnerable sub-dependency to a secure version or enforce a specific version if there are incompatibilities. It is also possible to completely replace individual packages within the dependency tree.

Especially in larger projects with deeply nested dependency trees, this is intended to significantly increase control. Security patches can be applied more quickly without having to wait for upstream updates. For teams with strict compliance requirements, this is an important building block.

Windows on ARM and more Node.js compatibility

In addition to the two core innovations, Deno 2.7 provides official builds for Windows on ARM (aarch64-pc-windows-msvc) for the first time. On devices such as the Surface Pro X or Snapdragon-based notebooks, Deno now runs natively – without an emulation layer and the associated performance losses.

The team is also significantly improving Node.js compatibility. Numerous adjustments in node:worker_threads, node:child_process, node:zlib, or node:sqlite close gaps to Node.js behavior. This is complemented by new or adapted APIs such as navigator.platform, SHA3 support in the Web Crypto API or Brotli support in CompressionStream and DecompressionStream.

More information is available in the blog post. Those who already use Deno can update as usual via deno upgrade. Just at the beginning of February, Deno had also made its serverless platform, Deno Deploy, generally available, strategically expanding the ecosystem around the runtime. (mdo)