Keynote: The State of npm
summary
NPM starts as a nights‑and‑weekends package manager and becomes a production service with five billion downloads in a month and about 320,000 modules available and roughly four million users. The team builds an enterprise registry and support for private modules, hardens ops after outages, splits the codebase into modules, improves CLI and website, and leans on semantic versioning; scaling surprises and operational reliability drive the move from hobby project to paid company infrastructure.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:542009: Node.js
- 1:26why this npm thing?
- 3:41Small Modules
- 8:13Why npm, Inc.? What does it do? Does it do things?? Let's find out! T
- 10:40the spice must flow
- 13:37Why conference?
- 14:39a few nice things
- 16:08npm, Inc.'s actual plans
related talks
10mInterview with Laurie Voss
41mHow the npm CLI Team Manages (Almost) 100 Open Source Projects
26mThe npm website: a tale of wonder and woe (and wombats!)
45mNext Gen Package Management
31mKeynote Panel: Node.js at Massive Scale
23mCover Your Apps While Still Using npm
38mThe economics of open source
37mNode.js Package Maintenance...