Skip to main content
← Guides

Guide

Node 22 vs Node 24: LTS Support and Upgrade Checks

Updated PkgPulse Team7 min read
0

Node 22 vs Node 24: compare LTS support dates, TypeScript and ESM changes, native addon risks, and upgrade checks before choosing a runtime for an application.

Contents

Between Node.js 22 and 24, choose 24 when your dependencies and hosting platform support it: its support window ends April 30, 2028, a year after 22. As of November 1, 2026, both are Maintenance LTS; Node 26 is Active LTS. Keep an existing Node 22 service while validating its upgrade, and evaluate Node 26 separately for new deployments.

Release lineStatus on November 1, 2026Initial releaseActive LTS startMaintenance startEnd of life
Node.js 22, JodMaintenance LTS2024-04-242024-10-292025-10-212027-04-30
Node.js 24, KryptonMaintenance LTS2025-05-062025-10-282026-10-202028-04-30
Node.js 26, LithiumActive LTS2026-05-052026-10-282027-10-202029-04-30

Source: Node.js Release Working Group schedule, accessed November 1, 2026 (UTC). Dates are scheduled support milestones and can change. An end-of-life date is not the end of Active LTS: Node 24 entered maintenance on October 20, 2026, while remaining supported until April 30, 2028.

Quick decision: Node 22 or Node 24?

SituationRecommendationCheck before deciding
Existing Node 22 production serviceTest 24 alongside 22, then schedule the migration before 22's EOLDependencies, integrations, deployment images and rollback
New deployment constrained to these two versionsPrefer 24 if the application passes validationHosting support and the exact package versions you use
Platform approved only for Node 22Keep 22 temporarily with an upgrade owner and deadlinePlatform approval and remaining support time
Native addons or legacy TLS integrationsRun a parallel compatibility trialBinary availability, build tools, certificates and trust configuration
Package author supporting Node 22 consumersRetain 22 coverage while adding 24 coverageMinimum engine policy and consumer requirements
New project without a version constraintInclude Active LTS Node 26 in the evaluationFramework, dependency and platform compatibility; LTS status alone is insufficient

These are planning recommendations, not measured compatibility results for your application. This guide keeps the Node 22 vs Node 24 comparison; the Node 24 migration checklist covers implementation steps.

What Maintenance LTS means for the decision

The Release Working Group's phase definitions, accessed November 1, 2026, describe maintenance releases as receiving critical bug fixes and security updates, with new features at the release team's discretion. Active LTS accepts a broader set of audited features, fixes and updates.

Node 22 is still supported. Node 24 gives a Node 22 team another year before the scheduled support deadline, but it is no longer the Active LTS line. Node 26 entered Active LTS on October 28, 2026. Avoid describing Node 24 as the universal current-LTS default or treating Node 26 as a future release.

For an existing service, use the support dates to set a migration deadline. Use tests, your provider's runtime policy and dependency documentation to choose the target. A later EOL date does not establish that a particular database driver, native module or deployment platform works with that runtime.

For historical context, the Node 20 to Node 22 upgrade guide covers the earlier transition. It does not replace the current support table above.

What changed from Node 22 to Node 24?

npm, V8 and Web APIs

The Node.js 24.0.0 release notes, accessed November 1, 2026, identify npm 11, V8 13.6, Undici 7 and a globally available URLPattern. V8 additions listed there include RegExp.escape() and Float16Array. These are release-specific facts; inspect the exact patch and image you intend to run rather than assuming every bundled component remains at its launch version.

const userInput = "react+dom (legacy)";
const safe = new RegExp(RegExp.escape(userInput));
console.log(safe.test("react+dom (legacy)")); // true

For npm projects, test installation using the existing lockfile before regenerating it. Record the npm version as well as the Node version so a package-manager change does not get mistaken for a runtime regression. For pnpm, Yarn or Bun projects, keep the project's own package manager and lockfile during the first trial.

Do not attach a generic speed multiplier to the V8 upgrade. Benchmark your application if performance is part of the migration case: use the same workload, machine limits, dependency versions and warm-up procedure on each runtime.

TypeScript support depends on the patch release

The Node 24 TypeScript documentation, accessed November 1, 2026, marks type stripping stable from v24.12.0. The Node 22 documentation, accessed the same day, records default enablement from v22.18.0 and labels the feature a release candidate. Describing all Node 22 releases as requiring a flag would therefore be misleading.

Both documents distinguish lightweight type stripping from full TypeScript tooling. It does not type-check the program or implement tsconfig.json behavior such as path aliases. Syntax requiring JavaScript generation needs additional handling; check the documented limits before replacing a runner.

// A script using erasable type annotations
const packageName: string = "pkgpulse";
console.log(`Refreshing ${packageName}`);

Keep type checking in CI, and leave your production compilation strategy unchanged during the runtime upgrade unless changing it is an explicit goal. This makes a failure easier to attribute.

CommonJS and ESM still need explicit tests

The Node 24 module documentation, accessed November 1, 2026, records that require(esm) is no longer experimental from v24.15.0. It also limits require() to synchronous ESM graphs: top-level await requires asynchronous loading.

Test your actual CLI entry points, configuration loaders and plugins. Do not replace every dynamic import() merely because the runtime supports some ESM loading through require(). Keep package module declarations explicit and test the package's public exports in the form consumers use.

Native addons and TLS deserve separate checks

The Node-API ABI documentation, accessed November 1, 2026, distinguishes Node-API's cross-version compatibility from direct V8 and Node C++ APIs, which can require updates or recompilation. Check the addon maintainer's supported runtimes and available binaries for your operating system and architecture.

The Node.js 24.5.0 release notes, accessed November 1, 2026, record the move to OpenSSL 3.5.1. Test TLS connections using the exact target image, CA configuration and client certificates. The bundled OpenSSL version alone does not prove that an integration will fail or that an application is secure.

Node 22 vs Node 24 comparison matrix

AreaNode.js 22Node.js 24
Support phase on November 1, 2026Maintenance LTSMaintenance LTS
Scheduled EOLApril 30, 2027April 30, 2028
Native TypeScript status in the accessed docsRelease candidate; enabled by default from 22.18.0Stable from 24.12.0
Existing production serviceKeep while the target is being testedMigration candidate after compatibility checks
New app limited to this pairUse when a concrete platform constraint requires itPreferred if dependencies and hosting support it
Package support policyRetain tests if consumers need 22Add tests before promising 24 compatibility

Lifecycle and feature rows use the official sources cited above. The application and package rows are this guide's decision framework; they are not claims of universal suitability.

Node 22 to Node 24 compatibility checklist

Before changing production, save the working Node 22 artifact, runtime configuration and dependency lockfile. Then run the same checks on the chosen Node 24 patch release.

SurfaceValidation taskEvidence to keep
InstallationInstall from the committed lockfile in a clean environmentNode/package-manager versions and install result
Native modulesExercise code that loads each addonPlatform, architecture and addon version
ESM/CJSRun CLIs, plugins, tests and config loadersEntry point and any loader error
HTTP clientsTest proxies, timeouts, redirects and streaming paths you useIntegration-test results
TLSConnect to staging equivalents of external servicesTrust settings and handshake result
TypeScriptRun scripts and the existing type checkerScript results and compiler output
DeploymentBuild and start the real imageImage identifier and smoke-test result

The Node 24.0.0 release notes also list runtime deprecations and removals, including url.parse() deprecation and tls.createSecurePair() removal. Review deprecation output rather than assuming a passing server start exercises every affected path. The migration guide gives a more detailed procedure.

Choosing an upgrade path by team

Existing Node 22 services

Add Node 24 to CI, fix demonstrated compatibility problems and exercise a staging deployment. Choose a rollout window with enough time to investigate failures before April 30, 2027. Keep rollback artifacts and document how to restore the old runtime; verify that the rollback still works after any separate database or configuration changes.

Package authors

Test the versions you claim to support. Make the minimum Node version explicit in package.json and release notes, and verify built exports from a consumer project. If raising the minimum removes a supported consumer runtime, explain that change through the package's release policy. An open-ended engine range is not proof that untested future majors work.

Platform teams and new projects

For a platform standardized on Node 24, publish the approved patch/image and track updates through its maintenance period. Give teams a separate compatibility process for Node 26 now that it is Active LTS. For a new project, validate the framework and hosting support matrix before choosing either version; do not copy a September 2026 default into a November decision.