A Pattern for a Well-Knit JavaScript Project
summary
Upgrading a React Native app from 55 to 74 (almost 20 versions) breaks many things and gets fixed by incremental steps: use npm why to find who depends on a package, run npm-check-updates or yarn upgrade interactive to classify patches/minors/majors, consult the React Native Upgrade Helper for config diffs, work on iOS and Android separately, use bleeding‑edge branches and small commits, and accept that a project of 72 packages needs selective upgrades and removal of unmaintained deps.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:48Freelancing and tangled deps
- 4:57Why dependencies matter
- 7:03Dependency types explained
- 9:56Community in dependency mgmt
- 11:41Debugging dependency issues
- 13:27Tooling debates for deps
- 15:33Monorepos and dep sharing
- 17:01React Native version upgrades
- 18:28Git bleeding edge branches
- 20:12Maintaining and letting go of dependencies
- 21:19Summary
related talks
23mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project
25mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project
20mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project
28mReal Strategies To Modernize a Legacy React Native Project
30mRefactoring large JavaScript codebases
28mLessons in Managing Technical Debt
31mRewriting a Large Hybrid App with React Native
41mThe Future of JavaScript Package Management