HISTORY OF DEV

May 30, 2017

Node.js 8 released

Node.jsA JavaScript runtime built on V8 — event-driven I/O for servers, CLIs, and tooling. 8.0.0 shipped on May 30, 2017 with V8Google's open-source JavaScript engine — powers Chrome, Node.js, and many embedded runtimes. 5.8 and npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. 5; native async/await had already been enabled by default in NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 7.6, and NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 8 became Active LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node. in October 2017.

What it was for

Node.jsNodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 8 became LTSLong-term support — a release branch maintained with security fixes for years, common in Linux and Node. in October 2017 — bringing native `async`/`await` to server JavaScript without transpilers. npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. 5 added package-lock.json by default, stabilizing dependency trees for millions of projects.

Why it's here

NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 8 made async/await the standard pattern for Node.jsA JavaScript runtime built on V8 — event-driven I/O for servers, CLIs, and tooling. servers.

Why it mattered

Native async syntax eliminated callback pyramids in production codebases.

What it solved

TeamsMicrosoft Teams — chat, video calls, and Office integration for workplace collaboration. transpiled async/await or chained Promises manually before NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 8.

Media

  • Node.js
    ImageNode.js

    Ryan Dahl, MIT, via Wikimedia Commons

Related