HISTORY OF DEV

April 26, 2016

Node.js 6 released

Node.jsA JavaScript runtime built on V8 — event-driven I/O for servers, CLIs, and tooling. 6.0.0 shipped on April 26, 2016 as a 'Current' release with V8Google's open-source JavaScript engine — powers Chrome, Node.js, and many embedded runtimes. 5.0 and an improved Buffer APIApplication programming interface — a defined way for programs to talk to each other or to a service.; it became Active LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node. in October 2016.

What it was for

Node.jsNodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 6 became LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node. in October 2016 — the stable line for Express, ReactA JavaScript library for building UIs — component trees and declarative rendering for the web. SSRServer-side rendering — HTML generated on the server for faster first paint and SEO., and early webpack ecosystems. Long-term support commitments gave enterprises confidence to standardize on NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. for APIs and build tooling.

Why it's here

NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 6 established the even-numbered LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node. pattern teams still follow today.

Why it mattered

Formal LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node. let companies plan multi-year NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. deployments.

What it solved

Production teams feared odd-numbered NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. releases would break without warning.

Media

  • Node.js
    ImageNode.js

    Ryan Dahl, MIT, via Wikimedia Commons

Related