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.
^18.19.1 || ^20.11.1 || ^22.0.0>=5.5.0 <5.7.0^6.5.3 || ^7.4.0ng update @angular/cli@~19.0 @angular/core@~19.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.
Components, directives and pipes default to standalone. Existing NgModule declarations need an explicit opt-out.
@Component({ selector: "app-example", template: "Hello" })
export class ExampleComponent {}// For a component still declared by an NgModule:
@Component({ standalone: false, selector: "app-example", template: "Hello" })
export class ExampleComponent {}Run the CLI migration, then check NgModule declarations for standalone: false.
Effects can run at different points in change detection. Tests that assumed microtask timing may need adjustment.
Exercise signal-driven components and wait for Angular stability before asserting asynchronous UI changes.
createComponent renders fallback content when projectableNodes contains an empty slot.
Check dynamic component projection. Pass an empty text node when deliberately suppressing fallback content.