How to save time & money by planning your ngUpgrade
summary
A decision framework lays out concrete criteria — team size, sprint capacity, architecture health, dependency triage, build and test posture — to pick between ngUpgrade, rewrite, hybrid routing or Angular Elements. It uses real numbers and examples (a nonprofit of 4 developers devoting 30% of each sprint versus an insurer with 70 developers and 10% capacity), names tools (TypeScript, CLI/Webpack, RxJS), and delivers a roadmap and cheat‑sheet at upgradingangularjs.com/angularconnect.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:23Migrating to BACKBONE.JS
- 1:54Use TypeScript. 2. Use Webpack. 3. ???? 4. Angular 2/4/5/6/10!
- 3:53Rewrite ngUpgrade Hybrid Router Elements
- 5:29We can't talk about code until we talk about people.
- 5:50Team Size
- 6:00devs • 2 medium apps • Coordination • No consulting
- 6:56Capacity
- 8:22Experience
- 10:16Your App (NITTY-GRITTY)
- 10:29Architecture
- 10:59Aligned with the style guide • Components • AngularJS 1.6
- 11:57Dependencies
- 14:14Build
- 14:57Gulp ES2015 € Babel
- 15:52BOTH NEED TO FACTOR IN TYPESCRIPT AND A BUNDLER!
- 16:06Testing
- 18:581. You're not alone. 2. You can do this.
related talks
20mBack from the past: A tale of helping others upgrade from Angular 1.x
20mAddicted to AngularJS?
05mConvince Your Boss to Upgrade in 5 Minutes
01h 01mAngular War Stories
20mUpgrading Enterprise Angular Applications
24mGetting to Angular 2
32mAngular Core Team Q&A
21mStreamlining the AngularJS-to-Angular migration