Untangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project
summary
Upgrading a React Native app from 0.55 to 0.74 reveals concrete pain points and fixes: uses yarn upgrade-interactive and npm why to trace transitive packages, runs the React Native Upgrade Helper to apply diffs, and uses knip, npm audit, Dependabot or Renovate for vuln patches. Break large failures into focused tasks iOS then Android, fix one compiler error at a time, and use bleeding‑edge branches to record work. Note autolinking lands at 0.60 and 72 packages need triage under semantic versioning rules.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 4:55About the speaker
- 7:22Understanding dependencies
- 10:41Community and tools
- 13:55Breaking down problems
- 15:44Monorepos and tools
- 17:33Security and automation
- 19:03Version control and upgrades
- 20:28How far to upgrade
- 21:32Final thoughts and resources
related talks
20mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project
25mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project
23mA Pattern for a Well-Knit JavaScript Project
10mStreamlining npm modules and lock files Management
30mRefactoring large JavaScript codebases
28mLessons in Managing Technical Debt
28mReal Strategies To Modernize a Legacy React Native Project
31mSolving a Tooling Problem For React Native