Migration Hub

Angular Upgrade & Migration Guide (v19 to v22)

Every version. Every breaking change. Straight to the fix.

By Antonio Cárdenas — Google Developer Expert in Angular

To upgrade Angular, move one major version at a time withng update @angular/cli @angular/core, after bringing Node.js and TypeScript up to the versions that release requires. The table below lists those requirements for each version, and every row links to the full migration guide.

Angular shipped a major every six months through v21. Since Angular 22 (June 2026) it ships one major per year, with Angular 23 expected around June 2027. Each major still introduces breaking changes that need both ng update schematics and manual code fixes.

Golden rule: Never skip a major version. Always migrate one step at a time: 19 → 20 → 21 → 22.
VersionReleaseNode.jsTypeScriptKey Shift
Angular 22 (Latest)Jun 202622.22.3+ / 24.15+ / 266.0.xOnPush default (Eager migration), Route params 'always'
Angular 21Nov 202520.19+ / 22.12+ / 24+5.9.xVitest default (Karma out), Zoneless default in new apps, ng mcp
Angular 20May 202520.11+ / 22.11+5.8+@angular/build (drops Webpack), stable Signals, afterEveryRender()
Angular 19Nov 202418.19+ / 20.11+5.5+Standalone by default, linkedSignal, resource() preview

How to Upgrade Angular: Step-by-Step Checklist

  1. Check angular.dev/update-guide for your exact version pair
  2. Verify your Node.js version meets the requirement (Angular 20–21 need Node 20.19+; Angular 22 needs Node 22.22.3+, 24.15+ or 26)
  3. Update TypeScript first — Angular 20 needs TypeScript 5.8+, Angular 21 needs 5.9, Angular 22 needs 6.0
  4. Commit all changes before running ng update — never run on a dirty tree
  5. Run ng update @angular/cli @angular/core — one major version at a time
  6. Run your test suite immediately after — breaking changes surface fastest here
  7. If using Karma, migrate to Vitest: ng generate @angular/core:karma-to-vitest

Frequently Asked Questions

How do I upgrade Angular to the latest version?

Run ng update @angular/cli @angular/core in your project root. Angular's update command handles dependency resolution and runs automatic migrations (schematics) that fix breaking changes in your code. Always check the Angular Update Guide at update.angular.io for version-specific steps and run the update one major version at a time — don't skip versions.

Can I skip major Angular versions when upgrading?

No. Angular's schematics run sequentially and depend on incremental migrations. Skipping from Angular 19 to Angular 21 directly will miss breaking-change migrations from v20, leaving your code in a broken state. Always upgrade one major version at a time: 19 → 20 → 21 → 22.

What are the biggest breaking changes from Angular 19 to 20?

The main Angular 20 breaking changes are: (1) afterRender() renamed to afterEveryRender() with no auto-migration; (2) TestBed.get() removed — use TestBed.inject(); (3) InjectFlags enum removed; (4) DOCUMENT token moved from @angular/common to @angular/core; (5) @angular-devkit/build-angular replaced by the new @angular/build package. Run ng update @angular/cli@20 @angular/core@20 for automatic migration.

What are the biggest breaking changes from Angular 20 to 21?

The main Angular 21 breaking changes are: (1) Karma is replaced by Vitest as the default test runner — run ng generate @angular/core:karma-to-vitest to migrate; (2) New apps exclude zone.js by default; (3) HttpClient is provided in the root injector by default. Migrate with ng update @angular/cli@21 @angular/core@21.

How long does an Angular migration take?

A standard Angular migration using ng update takes 15–60 minutes for most projects. Large enterprise apps with extensive Karma test suites or custom Webpack configurations may take 1–2 days, primarily due to migrating from Karma to Vitest. The schematics handle most of the boilerplate automatically.

Do I need to update TypeScript when upgrading Angular?

Yes. Each Angular major version requires a minimum TypeScript version. Angular 20 requires TypeScript 5.8+, Angular 21 requires TypeScript 5.9, and Angular 22 requires TypeScript 6.0 (>=6.0.0 <6.1.0), plus Node.js 22.22.3+, 24.15+ or 26. Always update TypeScript before running ng update to avoid compilation errors during migration.

What is the Angular release schedule?

Through Angular 21, Angular shipped a major release every six months (May and November). Starting with Angular 22 (released June 3, 2026), it ships one major every 12 months, with 4–6 minor releases in between; Angular 23 is expected around June 2027. Each major is typically supported for 24 months: 12 months active, then 12 months of LTS with critical and security fixes only. Angular 20 LTS ends November 28, 2026; Angular 21 is in LTS until June 2027.

Written by

Antonio Cárdenas

Google Developer Expert in Angular · 5 years running · Verified GDE profile · Google Developers profile · Highlighted by Angular on X

My technical writing reaches 100,000+ developers in English and Spanish. I've migrated production Angular apps from v8 to v22, and my open-source agentic skills are featured in community catalogs like agentic-awesome-skills.