Software

Node.js says all is forgiven, welcomes io.js fork back into the fold

Version 4.0.0 reunites code bases, adds features

By Neil McAllister in San Francisco

2 SHARE

The Node.js Foundation has released version 4.0.0 of the Node.js, the first version that reunites the JavaScript-based server-side web application framework with its io.js fork.

"This release represents countless hours of hard work encapsulated in both the Node.js project and the io.js project that are now combined in a single codebase," the Foundation said in a technical blog post announcing the release.

A number of major contributors to the Node.js open source project forked the code as io.js in December 2014 over conflicts with Joyent, Node.js's original parent company, regarding the project's governance model.

The io.js developers felt the code should be maintained by a formal technical committee, and that no single company should wield undue influence over it.

For a while, it looked as though Node.js and io.js would fly off on different trajectories. But the tensions eased when Joyent agreed to hand the reins of the Node.js project to an independent foundation created by a number of industry players.

In June, the two groups announced that they had mended their differences and would work to re-merge the code of the two projects – with a little help from the Linux Foundation, which now oversees the Node.js Foundation.

Tuesday's release of version 4.0.0 represents the first fruits of this effort, but it also brings a number of important changes to the Node.js project, both technical and in terms of governance.

One thing Node.js developers will notice right away is the version number. The last release of the framework was version 0.12, so the numbering has taken quite a leap. That's because the project's versioning will now conform to the Semantic Versioning (SemVer) specification – as did io.js – making it saner and more predictable.

On the technical front, the most important change is that Node.js now ships with version 4.5 of Google's V8 JavaScript engine, which is the same version that ships with the current Chrome browser. The main advantage of this is that version 4.5 supports a lot more features of ECMAScript 6 – the standard that will become the next version of JavaScript – giving Node.js developers greater flexibility and powerful new capabilities.

In addition, Node.js now has first-class support for ARM processors, including the 64-bit ARMv8 architecture. You can see a full list of changes from the old version in the technical blog post, here, and there's a list of changes that can break old code here.

On the governance side, although the Node.js maintainers say they won't be introducing any breaking changes within the 4.x branch of the code, they have begun work on a plan to offer long-term support (LTS) releases of the framework.

The idea, as of now, is that there will be a new LTS release every 12 months and they will each be actively maintained for 18 months. After the 18 months is up, they will enter "maintenance" mode for another 12 months, during which only critical bugs and security vulnerabilities will be fixed. More info on the proposed LTS policy is available on GitHub, here.

If all goes according to plan, the Node.js Foundation plans to ship its first LTS release in October. At the same time, work on the 5.x branch of the project will begin. ®

Sign up to our NewsletterGet IT in your inbox daily

2 Comments

More from The Register

I got 257 problems, and they're all open source: Report shines light on Wild West of software

It's like a jungle sometimes, it makes me wonder how I keep from going under

Microsoft ports its Quantum Development Kit to Linux and macOS

Now that it's not Windows-only, you can simulate a theoretical computer on a real computer

Everybody loves Microsoft's open switch software, SONiC

Roundup Plus news from F5, Palo Alto and Dell EMC in your networking news capsule

Open source community crams itself into big tent

Can't we just get along? At a sunny California inn with hors d'oeuvres, most definitely

They forked this one up: Microsoft modifies open-source code, blows hole in Windows Defender

Rar! That's a scary bug

'No, we are not rewriting Office in JavaScript' and other Microsoft tales

The week's good, bad and weird from Redmond

JS package catalog npm frees its team software for open source devs

With commercial success, npm can afford to be magnanimous

Open Source Security hit with bill for defamation claim

Judge okays $260K in defense costs to Bruce Perens and lawyers under anti-SLAPP

Microsoft loves Linux so much its R Open install script rm'd /bin/sh

Machine-learning suite ends its sloppy packaging ways after Debian dev roasts Redmond

Finally: Historic Eudora email code goes open source

'Member that innocent, pre-Zuckerberg time?