A How I learned to Stop Worrying and Let the Robot Publish to NPM
summary
Explains an automated CI/CD pattern called npm flow that publishes build artifacts per branch and keeps a human gate for mainline releases; uses the npm prepare lifecycle, .npmrc with an auth token in CI, and the npm version command so the robot bumps package.json, commits with a [ci skip] message, pushes back, and publishes tagged releases (e.g. next vs latest). Demonstrates npx cascadia.js and npx cascadia.js@next, runs in a mono-repo of ~20 packages with releases more than once a week.
AI-written summary · about
chapters (11)
- 0:00Introduction and thanks
- 1:13Bad package releases and open source
- 2:55CI/CD and testing confidence
- 4:59Git flow and branches explained
- 6:23Introducing NPM flow
- 8:54NPM tags and versioning
- 12:27Five keys to automation
- 14:15Automating versioning and releases
- 17:45Stable branch releases
- 19:50Overwhelming NPM with packages
- 20:16Q&A and closing remarks
related talks
19mKill all humans – Automate npm releases and dependency updates
41mHow the npm CLI Team Manages (Almost) 100 Open Source Projects
33mFrontend automation: bring it to the next level
43mContinuous Integration for Node.js with Jenkins
41mHandling Monorepos Today
38mThe npm workflow
17mA developer's take on security
18mAutomating All the Code & Testing Things with GitHub Actions