A Developer's Tale: Migrating an Angular app from version 10 to 18
summary
Real-world migration of the Devoxx CFP app from Angular 10 to 18 covers stepwise upgrades one major version at a time, using Node version managers (NVM/ASDF), ng update schematics, and commands like npm ls --all and npm outdated to map dependency pain points. Concrete problems include ngx-translate blocking 13.2, missing components copied into-repo, mismatched PostCSS versions fixed with npm dedupe, and occasional --force installs. The 10→17 run takes ~15–20 days (~2 days/version); later upgrades drop to hours.
AI-written summary · about
chapters (21)
- 0:00Introduction and story
- 1:28Why migrate Angular apps
- 3:56Preparing Node version
- 5:21Using NG update tool
- 7:30Cleaning dependencies
- 9:41Updating dependencies step by step
- 11:51Handling API changes
- 14:47Debugging dependency issues
- 16:36Fixing missing dependencies
- 18:22Copy-pasting libraries
- 19:47Finding duplicate dependencies
- 21:13Resolving version conflicts
- 24:02Migrating styles and CSS
- 25:50Migrating linters
- 27:15Linting deprecated APIs
- 28:18Leveraging Angular 18 features
- 31:51Migrating to standalone components
- 33:01Using AI for troubleshooting
- 34:08Automating updates with tools
- 36:14Key migration tips
- 39:28Q&A session
related talks
42mA Developer's Tale: Migrating an Angular app from version 10 to 17
27mAt the Heart of the Odyssey: Migrating an Application from Angular 10 to 17
22mClean Up Your Old Angular Apps!
26mUpgrading your AngularJS App, Without the Tears
13mMigrations - an Upgrade Story
24mMigrating from AngularJS to Angular
20mBack from the past: A tale of helping others upgrade from Angular 1.x
33mRefactoring 80+ Angular projects and what went wrong
