HISTORY OF DEV

January 12, 2010

npm first released

Isaac Schlueter released npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. 1.0 on January 12, 2010 — the default package manager for Node.jsA JavaScript runtime built on V8 — event-driven I/O for servers, CLIs, and tooling. (an earlier prototype was committed in September 2009).

What it was for

NpmnpmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. installs libraries with `npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. install express`, publishes packages to the registry, and locks versions in `package-lock.json`. It shaped how JavaScript shares code — from lodash to ReactA JavaScript library for building UIs — component trees and declarative rendering for the web. to corporate private registries. Every NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. project, frontend bundler, and CI install step depends on it.

People

  • Isaac Schlueter — creator

Why it's here

npmNode Package Manager — the default registry and CLI for installing JavaScript and TypeScript libraries. turned NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. from a runtime into an ecosystem with millions of reusable packages.

Why it mattered

It established semver, dependency trees, and publish workflows for modern JavaScript development.

What it solved

NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. had no standard way to discover, version, and install third-party modules.

Media

  • Npm
    ImageNpm

    Boboss74, Public domain, via Wikimedia Commons

Related