Migrations - an Upgrade Story
summary
Claims that an incremental rewrite centered on infrastructure fixes more than a full stop-and-rewrite: Hibob builds a UI component library (Storybook), a monorepo, and a custom light store powered by RxJS, then uses ngUpgrade to keep releasing features while migrating. They hit concrete problemsβlarge bundle size, lazy-loading pain, duplicated server calls from dual appsβbut shipping only Angular pages quickly and migrating with minimal changes speeds development, improves consistency, and ultimately succeeds as a pragmatic tradeoff.
AI-written summary Β· about
chapters (20)
- 0:00Introduction
- 1:03Agenda
- 1:25Introductions
- 2:14Backstory
- 2:38Web
- 2:57Legacy
- 3:10Why Angular
- 3:27Benefits
- 3:53Issues
- 4:29Example
- 5:04Migration Options
- 5:59Reframing Migrations
- 7:11Areas to Fix
- 8:01Three Steps
- 8:22Step 1 Infrastructure
- 9:03Step 2 UI Components
- 10:12Step 2 Benefits
- 11:03Before the Migration
- 11:46Migration
- 12:32Summary
related talks
44mMigrating to Angular 2
24mGetting to Angular 2
23mUpgrading to Angular without ngUpgrade
20mUpgrading Enterprise Angular Applications
24mMigrating from AngularJS to Angular
26mSTORE TREK: The Voyage to Angular
01h 00mUsing Monorepos for Scalable Apps
05mMigrating a Portfolio of Front-End Apps to Angular
