Node.js 22 entered Active LTS (Long-Term Support) status in October 2025, making it the recommended Node.js runtime for new production applications and the natural upgrade target for teams still running Node.js 18 or 20. In 2026, Node.js 22 LTS is the current runtime of choice for production Node.js deployments — combining the latest V8 engine improvements, meaningful performance gains, and several built-in features that previously required external packages.

This guide covers everything engineering teams need to know before upgrading: what is new, what changed under the hood, the performance benchmarks against earlier LTS versions, the migration considerations, and how to approach the upgrade safely for production systems.

What Is Node.js 22 LTS?

Node.js releases follow a predictable cadence. Even-numbered releases (18, 20, 22) become Long-Term Support versions, meaning they receive active bug fixes for 18 months followed by maintenance fixes for a further 18 months. Node.js 22 LTS is supported with active fixes until April 2027 and with maintenance releases until April 2028.

This schedule matters for production teams. Applications built on Node.js 22 LTS can expect security patches and critical bug fixes for the next two years — making it appropriate for production deployments that require stability and long-term vendor support.

Node.js 22 ships with V8 12.4 (the JavaScript engine from Chrome), libuv improvements for better I/O performance, and a set of stabilised APIs that were experimental in Node.js 20. Teams upgrading from Node.js 18 or 20 will find Node.js 22 largely compatible, with the breaking changes confined to internal APIs and deprecations that most applications do not directly use.

For enterprises and software teams building web applications, APIs, or microservices on Node.js, 2026 is the right time to standardise on Node.js 22 LTS if you have not already done so.

V8 Engine Upgrades in Node.js 22

The V8 JavaScript engine is the foundation of Node.js runtime performance. Node.js 22 ships with V8 12.4, a significant upgrade from the V8 11.3 included in Node.js 20 LTS.

The most impactful V8 changes in Node.js 22 are in garbage collection, compilation caching, and string operation optimisations. The new garbage collector in V8 12.4 reduces pause times for applications with high object allocation rates — a common pattern in API servers processing many concurrent requests.

Compilation caching improvements mean that JavaScript modules load faster on repeated invocations. For Lambda functions, container-based microservices, and any application pattern where startup time matters, this translates to measurable cold-start reductions.

String operations — particularly JSON parsing and serialisation — show the most dramatic improvements in isolated benchmarks. Applications that process large amounts of JSON (which is most Node.js API servers) will benefit immediately from the V8 12.4 upgrade without any code changes.

Performance Benchmarks: Node.js 18 vs 20 vs 22

In standard benchmarks comparing the three current LTS versions, Node.js 22 shows meaningful improvements across all three key metrics for web API servers.

HTTP request throughput improves from approximately 42,000 requests per second on Node.js 18 to 48,000 on Node.js 20, and to 56,000 on Node.js 22 — a 33% improvement from Node.js 18 to 22 and a 17% improvement from Node.js 20 to 22.

JSON parsing throughput improves from approximately 380 MB/s on Node.js 18 to 420 MB/s on Node.js 20 to 510 MB/s on Node.js 22 — a 34% improvement from 18 to 22. For applications that process large JSON payloads (REST APIs, data processing pipelines, webhook handlers), this is a free performance gain requiring no code changes.

Cold startup time reduction is where the difference is most pronounced for serverless and containerised deployments. Node.js 22 achieves approximately 28% faster startup compared to Node.js 18, meaning Lambda functions and container-based services respond faster to the first request after a cold start.

These benchmarks are from standard workloads; your specific application performance will vary based on code structure, dependency weight, and workload characteristics. However, the directional improvement is consistent across workload types — Node.js 22 is meaningfully faster than its predecessors.

New Built-In Features

Node.js 22 stabilises several APIs that were experimental in Node.js 20 and introduces new built-in capabilities that previously required external packages.

Native Test Runner

The Node.js test runner, introduced experimentally in Node.js 18, reaches stable status in Node.js 22. It supports parallel test execution, mock functions, spies, code coverage reporting, and TAP output format. For teams that have been using Jest or Mocha, the native test runner is not a full replacement in terms of ecosystem tooling — but for simpler testing needs, it eliminates a dependency.

Native Watch Mode

Node.js 22 includes stable watch mode via the --watch flag. Starting your application with node --watch index.js automatically restarts the process when source files change. For development workflows previously using nodemon or ts-node-dev, this is a built-in alternative that requires no additional packages.

Web APIs: Fetch, WebSocket, and ReadableStream

Node.js 22 ships with stable built-in implementations of the Fetch API, WebSocket client, and ReadableStream — aligning Node.js with the Web APIs that browsers expose. Teams building code that runs in both Node.js and browser environments benefit from improved isomorphic code patterns and fewer polyfill dependencies.

Improved ESM Support

ES module (ESM) support in Node.js has been iteratively improved across releases. Node.js 22 further reduces the friction between ESM and CommonJS modules, improving interoperability for projects migrating from CJS to ESM and for packages that need to support both module formats.

Security Enhancements and Permission Model

Node.js 22 includes improvements to the experimental permission model introduced in Node.js 20. The permission model provides a way to restrict what file system paths, child processes, and network destinations a Node.js process can access — useful for sandboxing untrusted code or enforcing least-privilege principles in server applications.

While still experimental in Node.js 22 and not recommended for production security-critical use without thorough testing, the permission model is maturing and is worth evaluating for security-sensitive deployments.

Standard security improvements in Node.js 22 include additional hardening of the DNS resolution layer, improved handling of edge cases in the HTTP parser, and updates to OpenSSL (which underpins Node.js TLS and cryptography). These improvements apply automatically on upgrade with no code changes required.

ESM and CJS Interoperability Improvements

One of the most practical improvements in Node.js 22 for teams maintaining large codebases is improved interoperability between ES modules and CommonJS modules. Node.js 22 makes it easier to require ESM modules from CJS contexts in more scenarios, and reduces the number of situations where module format mismatches cause runtime errors.

For teams with mixed codebases — or teams using packages that have moved to ESM-only — this is a meaningful quality-of-life improvement that reduces the need for workarounds and wrapper shims.

Migration Checklist: Upgrading to Node.js 22

Before upgrading production systems, work through this checklist to identify potential issues.

Update your runtime: change your Dockerfile base image, .nvmrc, or package.json engines field to Node.js 22. Run your complete test suite against Node.js 22 before proceeding further.

Audit native addons: if your application uses native Node.js addons (compiled C++ bindings), verify they have Node.js 22 compatible builds available. Most major native addons publish Node.js 22 compatible builds, but verify before upgrading.

Check for deprecated API usage: Node.js 22 removes some APIs that were deprecated in Node.js 18 and 20. Run your application with node --pending-deprecation to identify usage of APIs that may be removed in future versions.

Update CI/CD configuration: update your GitHub Actions, CircleCI, or other CI configuration to test against Node.js 22. Adding Node.js 22 to your test matrix before removing Node.js 20 allows you to identify issues without disrupting existing pipelines.

Monitor memory and performance after upgrade: after deploying to a staging environment, compare memory usage profiles and request latency to your Node.js 20 baseline. Node.js 22 generally uses less memory and runs faster, but unexpected differences can indicate version-specific code paths being triggered.

Running Node.js 22 in Production in 2026

For teams deploying Node.js in production in 2026, several operational considerations apply specifically to Node.js 22.

Container images: the official Node.js 22 Docker images are available on Docker Hub as node:22, node:22-slim, and node:22-alpine. The alpine variant provides the smallest image size. Use specific version tags (node:22.x.x) rather than the floating node:22 tag in production Dockerfiles to ensure reproducible builds.

Serverless deployments: AWS Lambda, Google Cloud Run, and Azure Functions all support Node.js 22 runtimes as of early 2026. The faster cold start times in Node.js 22 are particularly valuable for serverless deployments with variable traffic patterns.

Process management: use a process manager in production deployments outside of container orchestration. PM2 fully supports Node.js 22 and provides clustering, zero-downtime restarts, and memory monitoring. For container deployments, let your orchestrator handle process management.

Our Node.js development team at PapaSiddhi Technologies has completed Node.js 22 migrations for several enterprise clients in 2026. If you need support upgrading a complex production application, optimising Node.js 22 performance for your specific workload, or building a new application on Node.js 22 LTS, contact our team for an initial discussion.