The Node.js project released version 26 of the JavaScript runtime environment on [release date], marking a significant update that activates the Temporal API by default, upgrades the V8 JavaScript engine to version 14.6, and updates the Undici HTTP client to version 8.0. The release also removes several previously deprecated legacy APIs, prompting developers to review migration notes tied to changes in the NODE_MODULE_VERSION value.
Temporal API Now Active by Default
The Temporal API, a modern replacement for the JavaScript Date object, is now enabled by default in Node.js 26. This API provides improved handling of dates, times, time zones, and calendars with greater precision and consistency. Developers no longer need to use a command line flag to enable the feature, simplifying its adoption in production environments.
V8 Engine Updated to Version 14.6
The V8 engine, which powers JavaScript execution in Node.js, has been updated to version 14.6. This update includes performance improvements, bug fixes, and new JavaScript language features aligned with the latest ECMAScript specification. The upgrade is standard for major Node.js releases and aims to keep the runtime compatible with evolving web standards.
Undici HTTP Client Reaches Version 8.0
The Undici HTTP client, used for making network requests, has been upgraded to version 8.0. The new version introduces changes to request handling and error management. Users of Undici should review the changelog for specific API modifications that may require code updates.
Deprecated Legacy APIs Removed
Node.js 26 removes several legacy APIs that were previously marked as deprecated. The affected APIs include older modules and methods that have been replaced by more modern alternatives. The removal is part of a gradual cleanup process to reduce the codebase size and improve security. Developers are advised to check the official deprecation list and update their codebases accordingly.
NODE_MODULE_VERSION Change Requires Migration Attention
A notable technical change in Node.js 26 involves the NODE_MODULE_VERSION, an identifier used for native module compatibility. The version number has been incremented, meaning that native addons compiled for earlier Node.js releases will need to be recompiled for version 26. This change applies to any module that uses native C++ bindings, such as those built with node-gyp.
Release and Support Timeline
Node.js 26 is the current release and will remain in active development for six months before transitioning to Long Term Support (LTS) status. During this period, the project will release regular updates including patches and minor features. The LTS phase will provide extended stability and security fixes for production deployments, typically lasting 30 months.
Developers and organizations using Node.js should plan their upgrade cycles to accommodate the six month window before LTS begins. The Node.js project maintains a release schedule that allows for predictable transitions between major versions.
As the open source ecosystem continues to evolve, future Node.js releases are expected to include further optimizations to the V8 engine, additional API enhancements, and continued removal of legacy code. The project team has indicated that the focus remains on maintaining backward compatibility while modernizing the runtime for emerging development needs.
