Node.js is changing its release cycle, just as Chrome switches to weekly upgrades
Node.js, the popular open source and cross-platform JavaScript runtime, will have a less exciting release schedule in the future. There will now only be one major update to Node each year, just as its core engine from the Chromium project moves to weekly upgrades.
Node.js is used for many servers, web applications, scripts, and command-line tools, allowing JavaScript to be used in many software projects that might otherwise use PHP, Python, or Ruby. It is built on the V8 JavaScript engine, used in Google Chrome and other web browsers based on the Chromium project. There are usually two major releases each year, with a combination of Node-specific features and an updated version of V8.
The Node.js project announced that it was moving from two major releases per year to just one release per year. Instead of odd versions (v9, v11, etc.) becoming unsupported after six months, and even versions (v10, v12, etc.) serving as long-term support releases with 30 months of updates, each new major release will be a long-term support release.
There are several reasons for this change. The difference between even and odd versions can be confusing, and odd versions are never widely adopted, with most organizations ignoring them altogether. Node.js releases with long-term support are the most popular option, so it makes sense to only have those moving forward.
What is Chromium and can you use it as a browser?
Have you ever wondered what makes your web browser tick? If you peel back the layers, you’ll find something interesting at the core. Google Chrome is based on something called “Chromium”, and you may be surprised to see how many other browsers have this in common.
The blog post explained: “The current release schedule is 10 years old. It was created during the io.js merger to balance the needs of a growing ecosystem. As one contributor said at the time, it was an ‘educated estimate of what businesses would need.’ […] By reducing the number of concurrent release lines, we can focus on better supporting the versions people actually use.
This announcement comes a week after Google announced that the Chrome browser was moving to weekly releases, so that new features, performance improvements and bug fixes can be delivered more quickly. The V8 engine used by Node.js is managed as part of the Chromium project, so it will be updated as frequently as the Chrome browser.
If Chrome developers find a way to improve the performance of certain JavaScript or WebAssembly functions, those changes won’t make it to Node-based apps for months or a year. If the application is slow to update its copy of Node.js, it could take even longer for these improvements to be reflected. It’s not ideal, but it’s what the Node.js team can realistically handle, and most developers aren’t interested in living on the cutting edge anyway.
The new release schedule will begin with Node.js 27, which will enter alpha testing in October 2026, followed by a full release in April 2027. The LTS period will begin in October 2027 and support will end in April 2030.
Source: Knot Blog
