Node.js 24.x: What's New, Release History & Support Lifecycle

What Is New in Node.js 24?

Explicit Resource Management -- using and await using

Node.js 24 ships the TC39 Explicit Resource Management proposal natively via V8 13.6. The using and await using declarations automatically call a resource's [Symbol.dispose]() or [Symbol.asyncDispose]() method when the block exits -- regardless of whether it exits normally or via an exception.

// Synchronous resource -- auto-closes when block exits
{
  using handle = openFileHandle('./data.csv');
  const data = handle.read();
  // handle[Symbol.dispose]() called automatically here
}

// Async variant for database connections, etc.
async function query() {
  await using conn = await db.connect();
  return conn.execute('SELECT 1');
  // conn[Symbol.asyncDispose]() called automatically
}

This replaces the try/finally cleanup pattern. In practice it is most useful for file handles, database connections, locks, and any resource with a defined lifecycle. Node.js built-ins will add Symbol.dispose support incrementally in future releases.

New V8 13.6 JavaScript Features

Float16Array -- a new TypedArray for 16-bit floating-point numbers. Useful for machine learning inference (weights commonly stored as FP16), WebGPU interop, and memory-constrained numeric processing.

const weights = new Float16Array(1024); // half-precision floats
// Smaller memory footprint vs Float32Array

RegExp.escape(str) -- escapes a string so it can be safely inserted into a regex pattern without any character being interpreted as a quantifier or metacharacter.

const userInput = 'hello.world+test';
const pattern = new RegExp(RegExp.escape(userInput));
// No more manual replace(/[.*+?^${}()|[\]\\]/g, '\\$&')

Error.isError(value) -- reliably checks whether a value is an Error object across realm boundaries (iframes, workers), where instanceof Error can return false for errors from other contexts.

URLPattern Now a Global

URLPattern is available in the global scope -- no import required. It provides a standard pattern matching system for URLs using the same syntax as the URL Pattern API in browsers. This is useful for routing, middleware, and any code that needs to match URL shapes without setting up a full router.

const pattern = new URLPattern({ pathname: '/api/:version/users/:id' });
const match = pattern.exec('https://example.com/api/v2/users/42');
console.log(match?.pathname.groups); // { version: 'v2', id: '42' }

AsyncLocalStorage and AsyncContextFrame

AsyncLocalStorage now uses AsyncContextFrame as its default backend instead of the older async hooks mechanism. This improves performance, reduces overhead on the async context propagation path, and resolves edge-case correctness bugs.

For most users this is transparent. If you built tooling on top of AsyncLocalStorage internals or async_hooks directly, test your code on Node.js 24 -- the observable behavior of AsyncLocalStorage.getStore() is unchanged, but internal hook invocation timing may differ.

Permission Model and Test Runner Changes

The Permission Model flag changes from --experimental-permission to --permission, signaling its readiness for broader use. The permission system lets you restrict what filesystem paths, child processes, and native addons a Node.js process can access at startup.

node --permission --allow-fs-read=/data --allow-fs-write=/tmp server.js

The test runner auto-waits for subtests -- a breaking change. Previously t.test() returned a Promise you could await. In v24 that promise is removed; subtests are tracked and awaited automatically. Code that explicitly awaited subtest results needs updating.