Streamlining npm modules and lock files Management
summary
Shows concrete fixes: commit and never manually edit package-lock.json / yarn.lock / pnpm-lock.yaml, use tilde/caret for ranges, run yarn audit and yarn outdated and apply interactive upgrades, deduplicate dependencies and measure install/bundle size — projects with long neglect grow into mammoth node_modules with many duplicates and critical vulnerabilities. Recommends automating with Renovate bot (renovate.json, scheduled PRs, optional auto-merge) and running it per sprint; notes resolutions can pin transitive versions but use sparingly.
AI-written summary · about
chapters (8)
- 0:00Introduction and setup
- 1:10Talk overview and speaker intro
- 2:56Node modules and lock files basics
- 3:57Challenges with dependencies
- 5:02Maintaining lock files properly
- 6:27Streamlining node modules
- 7:53Automating dependency updates
- 9:18Renovate bot demo
related talks
23mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project
30mRefactoring large JavaScript codebases
57mZen and the Art of Package Management
16mDependency Hell Just Froze Over
16mSpeeding up the EcoSystem
23mA Pattern for a Well-Knit JavaScript Project
41mHandling Monorepos Today
41mThe Future of JavaScript Package Management