Dependency Hell Just Froze Over
summary
Node/npm ecosystem contains 180,000 modules and roughly 50,000 publishers, and that scale both enables productivity and creates breakage. A release-automation tool is built that writes changelogs and enforces heuristics: run old tests against new versions, run dependent projects’ tests via dont-break, abort releases on low coverage or vulnerabilities, and use Diffy and GitHub required status checks to detect regressions. Even a tiny router-login bot is shown working, proving these techniques catch and contain dependency breakage.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:27npm and student productivity
- 4:36JavaScript modules from zero
- 7:30Dependency hell's dark side
- 9:57Modules require responsibility
- 12:48Automating dependency tests
- 15:58Unfucking software culture
related talks
27mDependency hell - Or, Developers' perception of software dependencies
22mYou Don't Know Your Dependencies
30mWhat's Really Going on Inside Your Node_Modules Folder
24mManaging Dependencies with Confidence
25mThe node_modules Iceberg: Mysteries Below the Waterline
30mRefactoring large JavaScript codebases
35mThe Social Coding Contract
37mNode.js Package Maintenance...