Node.js 24 (Krypton) promoted to LTS — V8 13.6, npm 11, and a Windows toolchain shift

Key update

Node.js 24 (codename "Krypton") moved into Long‑Term Support on 2025‑10‑28. (nodejs.org) It consolidates several platform changes that affect production builds and CI: V8 upgraded to 13.6, npm upgraded to 11, URLPattern exposed globally, AsyncLocalStorage now defaults to AsyncContextFrame, Undici 7 included, and the experimental permission flag has been simplified to --permission. Critically for teams that build Node or native addons on Windows, MSVC support was removed and ClangCL is now required to compile Node from source. (nodejs.org) A known Buffer.allocUnsafe behavior (zero‑filled buffers) landed in the 24.x line but was fixed in the first LTS patch release (v24.11.1). (nodejs.org)

Why it matters

This is a practical migration milestone, not a cosmetic bump. Actionable impacts:

• Native modules and any code relying on V8 internals need rebuilds and verification because V8 13.6 bumps the ABI and introduces new globals; test and rebuild in staging. (nodejs.org)
• Windows CI images that previously assumed MSVC must be updated to provide ClangCL toolchains (or use official Node binaries) — failing to do so will break source builds and native addon compilation. (nodejs.org)
• Async context propagation and tracing/monitoring tools should be validated against the AsyncContextFrame default to detect subtle behavior changes in request/trace correlation. (nodejs.org)
• npm 11 and Undici 7 can affect install performance, lockfile behavior, and HTTP client semantics in CI/monorepo workflows — run CI jobs against a Node 24 LTS image to observe regressions early. (nodejs.org)
• Because a Buffer.allocUnsafe regression was present and then patched, pin your staging/production images to the first patched LTS (v24.11.1) and run low‑level crypto/KDF tests (e.g., pbkdf2 paths) before rolling out. (nodejs.org)

Source

• Source