How to Have an Amicable Breakup With a JavaScript Library
summary
Demonstrates that wrapping third party APIs lets a codebase swap libraries without mass edits or broken tests, using React and TypeScript with Grommet then Material UI, Superagent then native fetch, plus a Google Cloud Function backend for random pets. Builds a pet discovery app, replaces buttons cards and HTTP client live and the unit tests continue passing. Emphasizes prototyping multiple options as speed dating and codifying needs as wrapper components to make breakups tractable.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:26About Me
- 2:20What now?
- 4:17How to prepare for the inevitable future breakup?
- 7:22Prepare to bail on bad relationships
- 7:43The prenuptial agreement
- 14:37Prevent future mistakes
- 22:44Library opinions don't have to affect your code decisions
related talks
27mUnderstanding JavaScript Libraries via React and the React Ecosystem
28mLessons in Managing Technical Debt
46mHow to Evolve a Component Library Without Breaking It
24mThe missing guide for deciding between 3rd party library and custom code -JSWORLD 2023
20mMoving JS from Libraries to Polyfills
57mBuilding Scalable, Maintainable Apps Using TypeScript and React
28mBack to React: The Story of Two Apps
47mEmbrace the "react fatigue"