Node.js 22 Features: What's New, Breaking Changes & Should You Upgrade?

Introduction

The release of Node.js 22 in April 2024 marks a major milestone in the evolution of the world’s most popular JavaScript runtime. With V8 12.4, built-in WebStreams, single executable applications, and significant performance improvements, this version isn’t just an incremental update—it’s a leap forward.

But with great power comes great responsibility: Node.js 22 introduces breaking changes that can impact existing codebases. This in-depth guide explores every major Node.js 22 feature, highlights breaking changes, and helps you decide: Should you upgrade now—or wait?

Node.js 22 Release Overview

Node.js 22 is the latest Current release, entering Long Term Support (LTS) in October 2024 as Node.js 22.x (codename to be announced). It will be actively maintained until April 2026, with extended support until April 2027.

Key Highlights at a Glance

• V8 JavaScript engine 12.4

• Built-in Web Streams API (stable)

• Single executable applications (SEA)

• --experimental-require-module flag

• Default fetch() and WebSocket global

• Improved fs and stream performance

• ESM loader hooks stabilization

Top Node.js 22 Features You’ll Actually Use

1. Built-in Web Streams API (Stable)

No more npm install web-streams-polyfill. Web Streams are now stable and built into Node.js.

2. Global fetch() and WebSocket

No need for node-fetch or ws in most cases. Both are now available globally.

3. Single Executable Applications (SEA)

Bundle your entire app into a single binary—no source code exposure.

Performance Improvements in Node.js 22

V8 12.4: Up to 12% Faster Startup

Faster parsing, better JIT optimization, and reduced memory usage.

Stream and File System Optimizations

• fs.readFile now uses io_uring on Linux (up to 2x faster)

• stream.Readable memory usage reduced by ~30%

• Improved backpressure handling

Breaking Changes in Node.js 22: What You Must Know

Node.js 22 removes deprecated APIs and changes default behaviors. Here are the critical ones.

1. require() of ESM Modules Now Experimental

You can no longer require() an ESM-only module without --experimental-require-module.

2. Removed --experimental-policy

Integrity policies are now stable. Use --policy or NODE_OPTIONS.

3. URL Parsing Changes

new URL(input) now throws on invalid URLs (previously returned malformed object).

4. fs.promises Default Encoding Change

fs.promises.readFile() without encoding now returns Uint8Array instead of Buffer.

Should You Upgrade to Node.js 22?

Upgrade If:

• You’re starting a new project

• You want native fetch, WebSocket, or Streams

• You need SEA for CLI tools

• You’re on Node.js 18 (EOL April 2025)

• Performance is critical

Wait If:

• You rely on require() for ESM modules

• Your CI/CD isn’t ready for breaking changes

• You use --experimental-policy in production

• You’re on Node.js 20 LTS (supported until April 2026)

How to Upgrade Safely to Node.js 22

Step-by-Step Migration Plan

• Run node --version and check current version

• Use nvm or n to install Node.js 22 locally

• Run tests with NODE_OPTIONS=--experimental-require-module

• Audit dependencies with npm audit and depcheck

• Update package.json engines: "node": ">=22.0.0"

• Test in staging with real traffic

• Roll out gradually using feature flags

Node.js 22 vs Node.js 20: Detailed Comparison

| Feature | Node.js 20 | Node.js 22 | |--------|------------|----------------| | V8 Version | 11.3 | 12.4 (faster) | | fetch() | Experimental | Global & Stable | | Web Streams | Polyfill needed | Built-in | | SEA | Experimental | Stable | | ESM require() | Allowed | Requires flag | | LTS Until | Apr 2026 | Oct 2024 → Apr 2027 |

Real-World Use Cases for Node.js 22 Features

CLI Tools with SEA

Distribute your CLI as a single binary—no Node.js install required.

Edge Functions with Native fetch

Write Cloudflare Workers, Vercel Edge Functions, or Deno with zero dependencies.

Node.js 22 and the Future of JavaScript Runtimes

With Web Streams, fetch, and WebSocket now standard, Node.js is aligning closer with browser APIs. This reduces the gap between frontend and backend, enabling true full-stack JavaScript.

Conclusion

Node.js 22 is a must-upgrade for new projects and a smart upgrade for performance-critical apps. The built-in web APIs, SEA, and V8 improvements deliver real value—while breaking changes are manageable with proper testing.

Don’t wait for LTS. Start testing Node.js 22 in development today. Your future self (and your bundle size) will thank you.