Upgrading to Angular without ngUpgrade
summary
Upgrades happen one component at a time by packaging Angular components as Angular Elements, registering them with a tiny bridge called create-ng1-wrapper, and swapping in upgraded components without ngUpgrade or dual bootstrapping. Shared UI used by 13 teams migrates incrementally; core logic moves into framework-agnostic services that use window.fetch and return promises, then get wrapped for Angular (Observables) or AngularJS ($rootScope.$apply). Demo shows custom events, inputs/outputs, and route work across mixed apps.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:29Migration to Angular
- 3:49How do we get there?
- 4:30We are a component library....
- 7:33Bootstrapping Your Application
- 7:52Creating an Angular Element
- 9:03Custom Elements in AngularJS
- 12:10Add to an AngularJS Module
- 13:10AngularJS Template
- 13:34AngularJS Controller
- 16:39Angular Elements are Black Boxes
- 20:06Wrapping Agnostic Service
- 21:23What have we accomplished?
related talks
20mUpgrading Enterprise Angular Applications
20mAddicted to AngularJS?
24mGetting to Angular 2
05mMigrating a Portfolio of Front-End Apps to Angular
41mNG-NL 2017: Pete Bacon Darwin & George Kalpakas
44mMigrating to Angular 2
13mMigrations - an Upgrade Story
26mUpgrading your AngularJS App, Without the Tears
