The JavaScript platform Node.js has released Version 26, a major release, marks a new step in the evolution of the environment designed to run JavaScript code outside the browser. This is the new branch Current, which comes with a clear focus on modernizing the standard API and preparing the ecosystem for several years of support.
This new release Node.js 26.0.0 It is now available for download from the official website and is geared towards developers and teams who want to start testing the new features as soon as possible. Although it is currently considered an active development version, the project has already defined the timeline for transitioning it to a long-term support branch, something especially relevant for companies that rely on stable and predictable cycles.
Node.js Release Calendar and Support Cycle 26
Branch 26 is incorporated into the versions of long term supportBut it will do so in two phases: for approximately six months it will function as CurrentReceiving new features and adjustments, it will transition to LTS status in October after a code stabilization period. Once the transition is complete, the 26.x series will be maintained until May 2029, with security patches and bug fixes.
In parallel, the platform team maintains other branches with different end-of-life dates, which helps plan migrations in large projects. The family Node.js 24.x, also with extended support, will continue to receive updates until April 2028, while the 22.x branch is scheduled to end in April 2027. In contrast, the LTS 20.x line has already been taken out of maintenance and the intermediate version 25.x will cease to be supported at the beginning of June, pushing teams to make the jump to more recent series.
Temporal API: a new way of working with dates and times
The most visible change for those who program daily is the default activation of the Temporary API, a set of types and methods that offers a modern alternative to the veteran object DateThis API aims to simplify the management of dates and times, an area that has historically generated errors due to time zones, daylight saving time changes, and transformations between formats.
With Temporal, time can be represented in different ways depending on the specific needs of the project. For example, applications can handle dates and times without associating them with a specific time zone using types such as Temporary.PlainDate, Temporary.PlainTime y Temporary.PlainDateTime, useful for fixed schedules, reservations or registrations where only the local value matters.
When the context requires taking time zones into account, the API offers Temporal.ZonedDateTimeThis links the date and time to a specific time zone to ensure accurate calculations when traveling between regions or when applying time zone rules. Additionally, to store and compare absolute times, the following is introduced: Temporary.Instant, which represents a point in time as a number of nanoseconds since January 1, 1970, which is practical for distributed systems or audits.
Beyond data types, the API directly incorporates conversion, formatting, and time arithmetic operations, allowing you to add or subtract periods, change time zones, and generate readable output without relying on external libraries. The fact that Temporary comes enabled by default Node.js 26 facilitates its progressive adoption in projects that need reliable calendar management, from financial applications to logistics services.
V8 engine update and new JavaScript capabilities
Another key element of this release is the leap in the execution engine. V8 to version 14.6, the same line used in Chromium 146. This update not only brings performance improvements, but also additional language features and internal optimizations that impact application response time.
Among the new features that directly benefit developers, the possibility of combine multiple iterators into one using the method Iterator.concat()This capability simplifies the manipulation of data sequences from different sources without the need to create intermediate structures, which is useful when processing flows on servers that handle high volumes of information.
The engine also incorporates the specification of upsert for the collections Map y WeakMap In JavaScript. Thanks to this functionality, working with key/value pairs is more straightforward, as it is possible to insert or update entries in a single operation, reducing the amount of code required and minimizing potential race conditions in concurrent environments.
Undici 8 and improvements to the HTTP client
Regarding network communications, Node.js 26 updates the official HTTP client undici to the 8.x series. Specifically, various sources within the project indicate the adoption of version 8.0.2, which represents a step forward in stability, performance, and compatibility with the current needs of web APIs.
This client update is especially relevant for services deployed on infrastructure, where interaction with microservices, third-party platforms, and internal systems is constant. The new undici branch incorporates improvements in persistent connection management, updated support for HTTP/1.1 and HTTP/2, and resource consumption optimizations, which together reduce latency and make better use of available hardware.
Changes in compatibility and build requirements
The switch to Node.js 26 also comes with adjustments to the build environment and associated tools. Building this version from source requires, as minimum, GCC 13.2This move aligns the project with newer compilers and ensures the availability of modern binary-level optimizations. This change may require updates in continuous integration environments or build servers that are still using older versions of the tools.
In parallel, the new branch stops supporting Python 3.9 in its toolchain, meaning that configurations that depended on that version will need to migrate to more recent editions of the language. This decision is part of a broader effort to remove legacy dependencies and maintain the project's foundation on software that continues to receive security updates.
Deprecations and Retired APIs in Node.js 26
Along with the new features, the development team has introduced a series of compatibility changes that should be reviewed before migrating production projects. One of the points highlighted is the withdrawal of the method http.Server.prototype.writeHeader(), traditionally used to send HTTP headers from the server. Starting with this version, the official recommendation is to use http.Server.prototype.writeHead(), which remains the supported route.
Furthermore, this version marks the end of the cycle for DEP0182, related to the module cryptoas part of the routine process of cleaning up old or problematic APIs. The deprecation of module.register()This change will affect those working with more advanced or customized module loading systems, forcing a review of potential uses of this functionality.
The new branch also removes the boot option --experimental-transform-typesThis feature, which was part of the experimental set of features, has been removed. Its removal indicates that the team prefers to consolidate support for type transformations through other means or in later phases of the language and platform lifecycle, reducing the number of experimental flags.
Overall, the release of Node.js 26 represents a significant update to the ecosystem: it strengthens the time-based foundation with a modern API, updates the V8 engine, improves the HTTP client, and makes progress in cleaning up legacy interfaces. With support extending to 2029 and a clearly defined roadmap, the new version is shaping up to be a solid option for those seeking long-term stability without sacrificing the platform's latest capabilities.