The How, What and Why of Migrating to ReactJS
summary
A large Angular 1 ticketing app migrates incrementally to React using the Strangler application pattern, shipping a tiny React title component the day after starting and tackling larger pieces like the credit card form and a queues rewrite that takes a couple of weeks. Migration uses ngReact to embed components, moves tooling to Jest and webpack, runs 12‑minute acceptance tests (including IE), deploys daily, and shows Angular files dropping (126→80) while React files rise (122→159), with occasional production bugs.
AI-written summary · about
chapters (13)
- 0:00Introduction and context
- 3:54Choosing React for migration
- 6:00Strangler application approach
- 8:23Component-based migration strategy
- 11:13Testing during migration
- 13:45Managing the team and process
- 16:35Prioritizing migration work
- 19:46Release early and often
- 21:30Team knowledge sharing
- 24:20Upgrading tooling alongside migration
- 25:24Communicating with stakeholders
- 28:30Handling production issues
- 30:15Key takeaways and conclusion
related talks
31mLessons learned migrating complex software
32mMigrating from Angular to React
21mMigrating critical apps to React
16mAn Angular developer moving to React
31mReact on Rails
38mMigrating from PHP legacy code to React & Best Practices in React
01mAurora Scharff's Journey with React
10mHow to migrate 50,000 lines of code to React Server Components