Node.js 24 moves to LTS with V8 13.6, npm 11, ClangCL on Windows

Key update

Node.js 24 (released May 6, 2025) has moved into LTS as of October 2025. The release bundles V8 13.6 and npm 11, flips AsyncLocalStorage to use AsyncContextFrame by default, exposes URLPattern globally, upgrades the built-in HTTP client to Undici 7, and promotes the experimental permission model to a simpler --permission flag while removing MSVC support on Windows in favor of ClangCL. It also introduces semver-major changes (e.g., Float16Array, explicit resource management, WebAssembly Memory64) and a NODE_MODULE_VERSION bump that impacts native addons.

Why it matters

This is a production-grade platform shift you should plan for now. With Node 24 in LTS, teams should evaluate CI/build images, rebuild native modules, and run comprehensive test suites because the V8 upgrade and NODE_MODULE_VERSION change can break prebuilt binaries and native addons. Windows contributors and CI must switch toolchains to ClangCL; otherwise local builds and contributor onboarding will fail. The AsyncLocalStorage implementation change and improved permission flags can affect tracing, context propagation, and secure runtime workflows—verify observability and any tooling that relies on async context. The V8 additions (Float16Array, Memory64, RegExp.escape, Error.isError) and Undici 7 make Node 24 attractive for high-performance numeric workloads, WASM-based services, and modern HTTP features, but also mean auditing deprecated APIs (for example url.parse and SlowBuffer) and updating code where necessary. Operationally, pin container images to the exact Node 24.x LTS patch you validate, add a migration window in your release cadence, and treat this LTS as the baseline for new features and support going forward.

Source

• Source