Node.js 24 promoted to LTS (Oct 28, 2025) — V8 13.6, npm 11, tightened permissions, and an important Windows toolchain change

Key update

Node.js 24 was promoted to Long‑Term Support on October 28, 2025. The 24.x line upgrades the V8 engine to 13.6 and ships npm 11, makes URLPattern available globally, switches AsyncLocalStorage to use AsyncContextFrame by default, includes Undici 7, and stabilizes a simpler --permission CLI for restricted runtimes. Critically for build/CI environments, the Windows toolchain requirement changed: MSVC support was removed and ClangCL is now required to compile Node from source. (nodejs.org)

Why it matters

This is a practical production milestone you should treat as a migration window, not a cosmetic bump. The V8 and Undici updates improve runtime performance and WebAPI parity; npm 11 can change install performance and lockfile behavior in monorepos and CI; AsyncLocalStorage’s implementation change can surface subtle tracing/context-propagation differences in APMs; and the permission model gives a first‑class way to sandbox untrusted scripts. The Windows toolchain change is operationally disruptive for teams that build Node or native addons on Windows runners — update CI images and native build toolchains (or use official binaries) before moving to 24.x LTS. Also note an identified 24.x LTS issue where Buffer.allocUnsafe behavior differed from historical (uninitialized) expectations; validate low‑level memory assumptions and pin to the earliest patched 24.x release in staging until that is resolved. These are the concrete items teams should prioritize: test apps and native modules in staging, update CI/runner images (Windows), validate tracing/APM after AsyncLocalStorage changes, and evaluate npm 11 behavior in your monorepo flows. (nodejs.org)

Source

• Source