Compare Angular versions and see exactly what changes, what requires action, and what you can start using.
UpgradePath detects relevant tools and selects them automatically.
Select the tools in your project to include relevant dependency updates in this guide.
These guides cover each major's initial minor line (for example, 20.0.x). Commands select its latest patch. Later minors can have different toolchain ranges. Review the official update guide for the complete checklist.
^20.19.0 || ^22.12.0 || ^24.0.0>=5.9.0 <6.0.0^6.5.3 || ^7.4.0ng update @angular/cli@~21.0 @angular/core@~21.0Check this step's runtime first, review migration edits, then build and test before proceeding. Keep Angular core, compiler and CLI aligned. Update Material/CDK and other integrations with their own migrations when installed.
^22.22.3 || ^24.15.0 || ^26.0.0>=6.0.0 <6.1.0^6.5.3 || ^7.4.0ng update @angular/cli@~22.0 @angular/core@~22.0Check this step's runtime first, review migration edits, then build and test before proceeding. Keep Angular core, compiler and CLI aligned. Update Material/CDK and other integrations with their own migrations when installed.
Review code that depends on Zone.js notifications. The update migration preserves zone-based behavior where needed.
Review generated providers before removing Zone.js. Test UI updates, third-party integrations and async rendering.
Angular 21 introduces experimental signal-based forms alongside existing forms APIs.
Evaluate in an isolated feature; upgrading does not require rewriting existing forms.
Previously hidden type mismatches in host bindings can become compiler errors.
Build the application and correct incompatible host binding values.
Angular 22.0 requires the TypeScript 6.0 line. Earlier compiler versions are outside its supported range.
Let ng update coordinate the compiler packages, then build and type-check your application and libraries.
Angular 22.0 raises its supported Node.js versions. Check development, build and SSR environments.
Use a Node version from the requirement table before the 22.0 migration. Check CI images and deployment runtimes too.