Node.js 24 “Krypton” Is Now LTS: Your Upgrade Playbook

Node.js 24.21.0, codenamed “Krypton,” entered Long-Term Support on September 8, 2026. LTS is the line production teams should run, and Krypton is a strong one: a new V8 with modern language features, stable TypeScript type stripping, SQLite built in, and a permission model that keeps maturing. Here is what is new — and a playbook for upgrading without drama.

V8 13.6: the language grows up

Node 24 ships V8 13.6, and the language features it unlocks are genuinely useful day to day:

• Float16Array — half-precision floats for ML-adjacent and numeric workloads.
• Explicit resource management — using and await using with Symbol.dispose() give you deterministic cleanup, a pattern long familiar from other languages.
• RegExp.escape() — finally, a safe way to build regular expressions from user input without hand-rolled escaping.
• Error.isError() — reliable error checking that works across realms, where instanceof has always been fragile.

A more capable platform

Beyond the language, the platform keeps absorbing things that used to be dependencies. npm 11 ships with Node 24. URLPattern is now a global, so routing no longer needs a package. AsyncLocalStorage is built on AsyncContextFrame, making context propagation cheaper and more reliable — good news for tracing and request-scoped state. node:sqlite is built in, so lightweight persistence no longer needs a native addon. And the test runner keeps maturing: it now waits for subtests and offers context.log() for structured test output, which makes the built-in runner viable for more teams.

TypeScript without the build step

Type stripping for TypeScript is stable in Node 24 — you can run type-only TypeScript directly, with no compilation step. It only strips types, so features that require emit (like certain enum patterns) still need a build, but for a large class of services it removes the build step entirely. If your pipeline exists mostly to erase types, this simplifies it out of existence.

The permission model matures

Node’s permission model keeps maturing: permission.drop() lets running code shed privileges it no longer needs, and --permission-audit helps you discover what your dependencies actually touch. If you run untrusted code — or you simply want defense in depth for a large dependency tree — this is worth a serious evaluation on your next upgrade cycle.

Looking ahead: Node 26

Node 26 is the Current line, and it previews where LTS goes next: Temporal is enabled by default (the long-awaited modern date and time API), alongside V8 14.6 and Undici 8 for fetch. None of this is LTS yet, but it is a good reason to keep your upgrade muscles warm — the teams that upgrade routinely never face a scary multi-major jump.

Your upgrade playbook

Upgrading Node majors is routine if you treat it as a process rather than an event:

• Install Node 24 with your version manager and pin it in .nvmrc so every environment agrees.
• Run npm ci and your full test suite. Lockfile changes from npm 11 should be committed deliberately, after review — not swept in silently.
• Audit native addons. V8 13.6 can break modules compiled against older headers; rebuild and test them explicitly.
• Review permission flags if you use the experimental permission model today — the model has moved on.
• Smoke-test in staging with production-like load before promoting to production.

What the LTS label actually guarantees

Entering LTS means Node 24 now gets an extended support window: security patches and critical fixes on a predictable schedule, without the churn of the Current line. That is why production guidance is simple — run an LTS line, and treat Current as a preview of your next upgrade, not a deployment target.

It also means the ecosystem converges: framework majors, native addon vendors, and hosting platforms all target the LTS line. Upgrading to Krypton is not just about the features above — it is about rejoining the part of the ecosystem that gets the most testing.

“The teams that upgrade Node routinely never face a scary multi-major jump. Small, regular upgrades are the whole strategy.”

— DesignsToDeploy engineering notes

We run Node upgrades for client systems regularly — test suites, native addons, staging smoke tests, and all. If your services are still on Node 18 or 20 and the LTS clock is ticking, we can plan the move with you at designstodeploy.dev.