Migration Hub
Angular Upgrade & Migration Guide (v19 to v22)
Every version. Every breaking change. Straight to the fix.
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.
| Version | Release | Node.js | TypeScript | Key Shift |
|---|---|---|---|---|
| Angular 22 (Latest) | Jun 2026 | 22.22.3+ / 24.15+ / 26 | 6.0.x | OnPush default (Eager migration), Route params 'always' |
| Angular 21 | Nov 2025 | 20.19+ / 22.12+ / 24+ | 5.9.x | Vitest default (Karma out), Zoneless default in new apps, ng mcp |
| Angular 20 | May 2025 | 20.11+ / 22.11+ | 5.8+ | @angular/build (drops Webpack), stable Signals, afterEveryRender() |
| Angular 19 | Nov 2024 | 18.19+ / 20.11+ | 5.5+ | Standalone by default, linkedSignal, resource() preview |
Angular 19 → 20 Migration
Angular 20 replaces @angular-devkit/build-angular with the new @angular/buildpackage, drops Webpack, and makes Vitest the recommended test runner. Key manual fix: rename afterRender() to afterEveryRender().
Angular 19 to 20 Upgrade Guide: Breaking Changes & Fixes
Step-by-step guide to upgrade Angular 19 to 20: @angular/build replacing Webpack, Karma to Vitest fix, afterEveryRender(), and all breaking changes.
Read →How to Fix Karma in Angular 20: Missing Builder Error Solved
Angular 20 removed the Karma builder. Learn exactly how to restore it temporarily or migrate to Vitest in 5 minutes.
Read →Angular Migration Path: v15 to v21 Upgrade Guide
Step-by-step checklists for upgrading Angular v15 to v21. Covers standalone migration, Signals adoption, Karma removal, and per-version breaking changes.
Read →What's New in Angular 20: Stable Signals, TS 5.8 & Zoneless
Signals are stable, @angular/build drops Webpack, and Zoneless reaches developer preview. Every breaking change and new API in Angular 20 explained.
Read →Angular 20 → 21 Migration
Angular 21 kills Karma for good, makes zone.js opt-out in new projects, and introduces Signal Forms as an experimental API. Run ng generate @angular/core:karma-to-vitestbefore anything else.
Angular 20 to 21 Upgrade: Breaking Changes, Vitest & Fixes
Upgrade Angular 20 to 21 step by step: Karma to Vitest migration, zone.js opt-out, HttpClient root provider, and all breaking changes with CLI fixes.
Read →Angular MCP Server (ng mcp): Claude Code, Cursor & IDE Setup
Set up the Angular CLI MCP server (ng mcp) in Claude Code, Cursor, and VS Code for Angular 21 & 22. Full config JSON, all 8 MCP tools & zoneless migrations.
Read →Angular 21 → 22 Migration
Angular 22 makes OnPush the default change detection strategy, changes route parameter inheritance to 'always', and requires Node 22 + TypeScript 6.0. Signal Forms and the Resource APIs are now stable, and the framework treats AI agents as first-class collaborators.
Angular 21 to 22 Upgrade: Breaking Changes, Node 22 & Fixes
Upgrade Angular 21 to 22 step by step: OnPush default (ChangeDetectionStrategy.Eager), $safeNavigationMigration, route params, and Node 22 + TS 6.0 matrix.
Read →Angular 22 MCP + Skills: Build Agent-Safe Components
Stop agents from shipping broken code. Set up Angular 22 MCP + Skills in 5 minutes, apply 4 proven patterns, and let agents verify their own changes.
Read →Angular 22: Stop Agent Hallucinations with @boundary
Angular 22 closes the hallucination loop with @boundary isolation, exhaustive types, and MCP-verified builds. Full breakdown from Google I/O 2026.
Read →How to Upgrade Angular: Step-by-Step Checklist
- Check angular.dev/update-guide for your exact version pair
- 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)
- Update TypeScript first — Angular 20 needs TypeScript 5.8+, Angular 21 needs 5.9, Angular 22 needs 6.0
- Commit all changes before running
ng update— never run on a dirty tree - Run
ng update @angular/cli @angular/core— one major version at a time - Run your test suite immediately after — breaking changes surface fastest here
- 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.