Integrating React Into Legacy Projects
summary
A concrete migration path: build small CDN-hosted plugin bundles that implement a clear data → parser → state → UI flow, keep one React version, publish a core library plus a configuration package, and enforce 80% test coverage. The legacy site already serves 20,000+ live events/month with VBScript and a monolith, so rewriting is impractical; the team ships independent feature bundles, manages shared deps centrally, and deploys working React blocks to production via CDN integration.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:35Technical Difficulties
- 2:25What is Legacy
- 4:55Perception
- 10:00Continuous Feature Development
- 14:15Challenges
- 15:57Mocks
- 22:03Architecture
- 24:52Implementation
- 31:05Data Facade
- 32:38Project Architecture
- 35:54QA Session
related talks
28mLessons in Managing Technical Debt
10mHow to migrate 50,000 lines of code to React Server Components
21mMigrating critical apps to React
13mSpeed at Scale: Optimizing The Largest CX Platform Out There
32mThe How, What and Why of Migrating to ReactJS
20mWhen Old meets New: Codebases
28mBack to React: The Story of Two Apps
31mReact on Rails