September 8, 2015
Node.js 4.0 released
Node.jsA JavaScript runtime built on V8 — event-driven I/O for servers, CLIs, and tooling. 4.0.0 shipped on September 8, 2015, merging the io.js fork back into NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. with V8Google's open-source JavaScript engine — powers Chrome, Node.js, and many embedded runtimes. 4.5 and native ES6 support; the first official LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node. line began with 4.2.0 'Argon' in October 2015.
What it was for
NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 4 ended the io.js schism and established even-numbered LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node. releases. Arrow functions, classes, and template literals worked natively; npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. 2 shipped bundled. It became the baseline for Express, Koa, and the MEAN/MERN stacks of the mid-2010s.
Why it's here
NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 4 reunited the community after the io.js fork and defined modern NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node..
Why it mattered
The LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node. policy gave enterprises a stable line while odd versions experimented.
What it solved
The io.js fork split contributors and left production teams unsure which runtime to ship.
Media
- ImageNode.js
Ryan Dahl, MIT, via Wikimedia Commons
Related
- Node.js 0.10 releasedMarch 11, 2013
- Node.js first releasedMay 27, 2009