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

Version 4.0.0 reunites code bases, adds features

2 Reg comments Got Tips?

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. ®

SUBSCRIBE TO OUR WEEKLY TECH NEWSLETTER


Keep Reading

Oracle teases prospect of playing nicely with open-source Java in update to WebLogic application server

'Low cost of ownership'? This must be an April Fools

NPM today stands for Now Pay Me: JavaScript packaging biz debuts conduit for funding open-source coders

Like a particular module? You're one command away from being able to donate some dosh for it

AppGet 'really helped us,' Microsoft says, but offers no apology to dev for killing open-source package manager

Windows bod acknowledges project's influence on WinGet

Microsoft's GitHub absorbs NPM into its code-hosting empire: JavaScript library vault used by 12 million devs now under Redmond's roof

Developers! Developers! Developers! And all their infrastructure!

Nine in ten biz applications harbor out-of-date, unsupported, insecure open-source code, study shows

Free-as-in-speech software is wildly popular – keeping libraries, components up to date is not

.NET Core: Still a Microsoft platform thing despite more than five years open source

Comment Making .NET cross-platform was a radical step but not enough for broad appeal

Everything OK with Microsoft? Windows giant admits it was 'on the wrong side of history' with regard to open source

Tell-all with president Brad Smith reveals Obama warned tech giants that a privacy reckoning was coming

When one open-source package riddled with vulns pulls in dozens of others, what's a dev to do?

Snyk survey puts cross-site scripting top of the list for security holes – but watch out for prototype pollution too

Biting the hand that feeds IT © 1998–2020