Node.js 26 Released: What’s New

Node.js 26 was released on May 5, 2026, as the new Current release in the Node.js long-term support (LTS) cycle. The release upgrades the V8 JavaScript engine to version 14.6, enables the Temporal date/time API by default, and removes several legacy APIs that have been deprecated for multiple major versions. If you run Node.js applications on your InMotion Hosting server, here is what changed and what to check before you upgrade.

What’s New in Node.js 26

Node.js 26 ships a combination of JavaScript engine improvements, new platform APIs, and long-overdue cleanup of legacy internals. The changes most likely to affect application code are covered below.

V8 engine updated to 14.6

Node.js 26 ships V8 version 14.6.202.33, drawn from Chromium 146. This engine update brings two new JavaScript language features that land directly in your application code without any flags or polyfills.

Map and WeakMap upsert methods. The new getOrInsert() and getOrInsertComputed() methods let you atomically check for a key and insert a default value if it is missing. This pattern appears frequently in caching layers and memoization utilities.

const cache = new Map();

// Returns the existing value, or inserts and returns the default
const value = cache.getOrInsert('session-key', defaultSession);

// Computed variant: the factory runs only if the key is absent
const data = cache.getOrInsertComputed('user-42', (key) => fetchUser(key));

Iterator sequencing. The new static Iterator.concat() method combines multiple iterators into a single lazy sequence, which can reduce intermediate allocations when processing streams or collections.

const combined = Iterator.concat(iteratorA, iteratorB, iteratorC);
for (const item of combined) {
  process(item);
}

Temporal API enabled by default

The Temporal API, the modern replacement for the Date object, is now enabled globally in Node.js 26 without any --harmony flags. Temporal provides unambiguous date, time, and time zone handling that avoids the well-known pitfalls of Date: mutable objects, implicit local time zone coercion, and inconsistent month indexing. If your application uses a date library like Day.js or date-fns mainly to work around those Date limitations, Temporal may reduce that dependency.

// Get the current instant in UTC (no timezone ambiguity)
const now = Temporal.Now.instant();

// Create a date in a specific timezone
const meeting = Temporal.ZonedDateTime.from(
  '2026-06-15T14:00:00[America/New_York]'
);

console.log(meeting.toLocaleString('en-US', { timeZone: 'America/Chicago' }));

Removed legacy stream internals

Node.js 26 removes the internal _stream_* modules that have been marked deprecated for years. The removed modules are:

• _stream_wrap
• _stream_readable
• _stream_writable
• _stream_duplex
• _stream_transform
• _stream_passthrough

Any package that requires these modules directly will break on Node.js 26. The correct replacement is to import from the stream module: require('stream').Readable, require('stream').Writable, and so on. Run npm outdated and check your dependency tree for packages that have not been updated since Node.js 16 or earlier, as those are the most likely to reference these internals.

Important: Readable streams also change behavior in Node.js 26: they now read one buffer at a time instead of reading ahead. Applications that depend on the old buffering behavior may experience changes in throughput. Test your stream-heavy code paths before upgrading in production.

Other notable removals and deprecations

Several additional APIs changed status in this release:

• HTTP: http.Server.prototype.writeHeader() is removed. Use writeHead() instead.
• Module: The --experimental-transform-types flag is removed. TypeScript type stripping, previously governed by the flag, is now part of the stable module system.
• Module: The extensionless CJS exception for packages using "type": "module" is removed. Files without an extension in a type: module package now require an explicit .cjs or .mjs extension.
• Module: module.register() is now runtime-deprecated.
• Crypto: ML-KEM and ML-DSA keys default to seed-only format for PKCS8 export.

What This Means for Your Hosting

Node.js 26 launched as a Current release, not a Long-Term Support (LTS) release. Even-numbered Node.js versions follow a standard schedule: after roughly six months as Current, they transition to Active LTS status. The official release post states that Node.js 26 will enter LTS in October 2026. Active LTS receives bug fixes and security patches for 18 months, followed by a Maintenance phase for critical security fixes until end-of-life. See the Node.js release schedule for the canonical timeline.

For production applications that require stability, Node.js 24 is the current Active LTS release and Node.js 22 is in Maintenance LTS. Node.js 26 is best suited for development environments and testing until it reaches LTS status.

Node.js 26 is a brand-new release. Managed hosting environments, including InMotion Hosting’s shared and cPanel-based plans, take time to package, test, and roll out new Node.js versions.

cPanel and shared hosting customers can check which Node.js versions are currently available by logging in to cPanel and opening Setup Node.js App under the Software section. The versions listed there are the ones InMotion Hosting has packaged and made available for your plan. If Node.js 26 does not appear, it has not been added yet. The Setup Node.js App tool is available on Nginx shared plans; for full setup steps, see How To Set Up Node.js App in cPanel.

VPS and Dedicated Server customers on self-managed plans can install any Node.js version directly. You can install Node.js 26 using nvm (Node Version Manager), via official binaries from nodejs.org, or through the NodeSource repository. If you are not sure whether your VPS plan is self-managed or managed, contact InMotion Hosting support.

Note: InMotion Hosting has not announced a specific timeline for adding Node.js 26 to the cPanel Setup Node.js App selector on managed plans. Check the selector and contact support if you have a specific deployment requirement.

How to Get Started with Node.js 26

If you are on a VPS or Dedicated Server and want to install Node.js 26, nvm is the most flexible path. It lets you run multiple Node.js versions side by side and switch between them per project.

Install or Update nvm

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bash

Install Node.js 26

nvm install 26

Switch to Node.js 26 for the current session

nvm use 26

Verify the installation

node --version

Before upgrading an existing application, check your dependencies for any that rely on the removed _stream_* internals or the deprecated writeHeader() method. Running your test suite against a Node.js 26 environment is the most reliable way to surface incompatibilities before they reach production.

For the complete list of changes, including all breaking changes and deprecation notices, see the official Node.js 26.0.0 release post.