How the npm CLI Team Manages (Almost) 100 Open Source Projects
summary
A four‑person effort runs about 78 repos that account for 4.3 billion monthly downloads, using templating, standard linting/CHANGELOG conventions, and auto-publish via GitHub workflows to get roughly 12.5 releases per week across the portfolio. Built tools include a public status board that tracks health, templating + dependabot loops to propagate changes, and nightly CI across Node versions; automation reduces churn but human gating remains for the CLI after a manual publish mistake once broke installs.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:25Team responsibilities and scale
- 5:40Open source philosophy
- 10:37Collaborative practices
- 13:30Deprecating projects
- 18:08User confidence in open source
- 21:17Managing large portfolios
- 27:17Automating consistency
- 31:54Measuring processes
- 35:47Transparent processes
- 37:10Automation tools
- 40:20Summary and collaborate
