March 11, 2013
Node.js 0.10 released
Node.jsA JavaScript runtime built on V8 — event-driven I/O for servers, CLIs, and tooling. 0.10 shipped on March 11, 2013 with stable streams, domains for error handling, and the foundation for npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries.'s explosive growth.
What it was for
NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 0.10 was the first long-lived stable line for production: the streams2 APIApplication programming interface — a defined way for programs to talk to each other or to a service. made piping data reliable; domains helped catch async errors. It powered the early npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. ecosystem — Express, Socket.io, and Grunt all targeted 0.10.
Why it's here
NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. 0.10 was the version that made Node.jsA JavaScript runtime built on V8 — event-driven I/O for servers, CLIs, and tooling. credible for production servers.
Why it mattered
Stable streams and a predictable release line accelerated npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. package adoption.
What it solved
Earlier 0.x releases broke APIs too often for enterprises to commit.
Media
- ImageNode.js
Ryan Dahl, MIT, via Wikimedia Commons
Related
- Node.js first releasedMay 27, 2009