Angular Upgrade Planner
Pick a source and target Angular version (8–22) for an ordered, checkable upgrade plan — ng update commands, breaking changes, deprecations, and migrations.
Choose your upgrade path
Angular 10 → Angular 11
(5 steps)Commit or stash all work, then make sure you are on the latest minor/patch of your current major before running ng update. Upgrade exactly one major at a time and run the app/tests after each hop.
Angular 11 requires TypeScript 4.0 and drops support for IE9, IE10, and IE mobile.
Check your Node.js & TypeScript versions for Angular 11 →Update the core framework and CLI together. This applies the official automatic migration schematics for this version.
ng update @angular/core@11 @angular/cli@11
Some async test helpers and CollectionChangeRecord are deprecated. Update to the recommended TestBed patterns.
webpack 5 support is available (experimental) via a package.json resolutions entry. Hot Module Replacement can be enabled with ng serve --hmr. Automatic inline fonts and faster builds are included.
Sources: Angular Update Guide: v10 → v11 · Angular 11.0.0 release notes
Angular 11 → Angular 12
(5 steps)Commit or stash all work, then make sure you are on the latest minor/patch of your current major before running ng update. Upgrade exactly one major at a time and run the app/tests after each hop.
Angular 12 requires Node.js 12.14 or newer and TypeScript 4.2+.
Check your Node.js & TypeScript versions for Angular 12 →Update the core framework and CLI together. This applies the official automatic migration schematics for this version.
ng update @angular/core@12 @angular/cli@12
Angular 12 deprecates View Engine; the framework is effectively Ivy-only going forward. Production build becomes the default for ng build, and IE11 support is deprecated.
node-sass is no longer supported. Run the Sass migration and switch your styles to dart-sass. Nullish coalescing (??) is now supported in templates.
Sources: Angular Update Guide: v11 → v12 · Angular 12.0.0 release notes
Angular 12 → Angular 13
(5 steps)Commit or stash all work, then make sure you are on the latest minor/patch of your current major before running ng update. Upgrade exactly one major at a time and run the app/tests after each hop.
Angular 13 requires a current Node.js (12.20+, 14.15+, or 16.10+) and TypeScript 4.4. New apps get RxJS 7.4; existing apps can stay on RxJS 6.5+.
Check your Node.js & TypeScript versions for Angular 13 →Update the core framework and CLI together. This applies the official automatic migration schematics for this version.
ng update @angular/core@13 @angular/cli@13
View Engine is removed from the framework and libraries are now published in Ivy partial-compilation format. Older View Engine libraries still work through ngcc until v16. Internet Explorer 11 support is removed, and string-based loadChildren must use dynamic import().
ModuleWithProviders now requires a generic type, entryComponents is no longer needed/used, and renderModuleFactory is removed. The migration fixes most of these automatically.
Sources: Angular Update Guide: v12 → v13 · Angular 13.0.0 release notes
Angular 13 → Angular 14
(5 steps)Commit or stash all work, then make sure you are on the latest minor/patch of your current major before running ng update. Upgrade exactly one major at a time and run the app/tests after each hop.
Angular 14 requires Node.js 14.15+ or 16.10+ and TypeScript 4.6 to 4.8.
Check your Node.js & TypeScript versions for Angular 14 →Update the core framework and CLI together. This applies the official automatic migration schematics for this version.
ng update @angular/core@14 @angular/cli@14
FormControl, FormGroup, and FormArray are now strictly typed. Existing forms code may stop compiling; the migration swaps to Untyped* variants so you can adopt typing gradually.
Standalone components/directives/pipes arrive in developer preview, along with the inject() function, NgOptimizedImage (preview), functional Router guards (CanMatch), and the page Title strategy.
Convert constructor injection to inject() online →Sources: Angular Update Guide: v13 → v14 · Angular 14.0.0 release notes
Angular 14 → Angular 15
(5 steps)Commit or stash all work, then make sure you are on the latest minor/patch of your current major before running ng update. Upgrade exactly one major at a time and run the app/tests after each hop.
Angular 15 requires a current Node.js (14.20+, 16.13+, or 18.10+) and TypeScript 4.8 or 4.9.
Check your Node.js & TypeScript versions for Angular 15 →Update the core framework and CLI together. This applies the official automatic migration schematics for this version.
ng update @angular/core@15 @angular/cli@15
Angular Material components are rebuilt on Material Design Components (MDC). DOM structure and CSS change — audit custom Material styles and run the Material migration. Legacy components are available under @angular/material/legacy-* temporarily.
bootstrapApplication, provideRouter, provideHttpClient, functional Router guards, the directive composition API, and NgOptimizedImage are all stable. Consider adopting standalone bootstrap.
Sources: Angular Update Guide: v14 → v15 · Angular 15.0.0 release notes
Angular 15 → Angular 16
(6 steps)Commit or stash all work, then make sure you are on the latest minor/patch of your current major before running ng update. Upgrade exactly one major at a time and run the app/tests after each hop.
Angular 16 requires Node.js 16.14+ or 18.10+ and TypeScript 4.9.3 up to 5.1.
Check your Node.js & TypeScript versions for Angular 16 →Update the core framework and CLI together. This applies the official automatic migration schematics for this version.
ng update @angular/core@16 @angular/cli@16
Non-destructive hydration is available in developer preview with provideClientHydration (SSR still uses @nguniversal in v16). An esbuild-based build and dev server is also in developer preview.
The Angular Compatibility Compiler (ngcc) is removed, so any dependency still shipped in View Engine format fails to build. Update or replace those libraries before this hop.
Angular Signals arrive in developer preview, along with takeUntilDestroyed/DestroyRef, required inputs, and binding Router data/params/title to component inputs via withComponentInputBinding. Self-closing tags are supported.
Sources: Angular Update Guide: v15 → v16 · Angular 16.0.0 release notes
Angular 16 → Angular 17
(6 steps)Commit or stash all work, then make sure you are on the latest minor/patch of your current major before running ng update. Upgrade exactly one major at a time and run the app/tests after each hop.
Angular 17 requires Node.js 18.13+ or 20.9+ and TypeScript 5.2 up to 5.4.
Check your Node.js & TypeScript versions for Angular 17 →Update the core framework and CLI together. This applies the official automatic migration schematics for this version.
ng update @angular/core@17 @angular/cli@17
New applications use the esbuild + Vite application builder (@angular-devkit/build-angular:application) with faster builds and a Vite dev server. Existing apps keep the webpack builder until migrated. SSR moves to the new @angular/ssr package and is offered during ng new.
New built-in control flow replaces *ngIf/*ngFor/*ngSwitch — run ng generate @angular/core:control-flow to migrate templates. Deferrable views (@defer) enable lazy loading of template blocks.
Convert a template to @if/@for online →ng generate @angular/core:control-flow
signal() and computed() are stable (effect() stays in developer preview until v20), afterRender/afterNextRender hooks are added in developer preview, and the View Transitions API is supported via withViewTransitions.
Sources: Angular Update Guide: v16 → v17 · Angular 17.0.0 release notes
Angular 17 → Angular 18
(5 steps)Commit or stash all work, then make sure you are on the latest minor/patch of your current major before running ng update. Upgrade exactly one major at a time and run the app/tests after each hop.
Angular 18 requires Node.js 18.19.1+, 20.11.1+, or 22, and TypeScript 5.4 or 5.5.
Check your Node.js & TypeScript versions for Angular 18 →Update the core framework and CLI together. This applies the official automatic migration schematics for this version.
ng update @angular/core@18 @angular/cli@18
provideExperimentalZonelessChangeDetection lets you trial zoneless apps, and event replay for SSR is available in preview. Review zone-dependent code before trying zoneless.
Angular Material 3 is stable, the build tooling is published as @angular/build, deferrable views and built-in control flow are stable, ng-content supports default/fallback content, and route redirects can be functions.
Sources: Angular Update Guide: v17 → v18 · Angular 18.0.0 release notes
Tip: Upgrade one major at a time and run ng update for each hop — it applies the official migration schematics automatically. Commit between hops and run your tests. This is a representative checklist of the major changes; always confirm specifics against the official Angular Update Guide for your exact versions.
Upgrading Angular 10 to Angular 18
This plan covers the full path from Angular 10 to Angular 18 — 8 version hops and 42 steps in total. Upgrade one major at a time, running ng update for each hop so the official migration schematics apply. Commit and run your tests between hops.
Breaking changes to check between Angular 10 and Angular 18
- View Engine is deprecated — Ivy only (Angular 11 → Angular 12): Angular 12 deprecates View Engine; the framework is effectively Ivy-only going forward. Production build becomes the default for ng build, and IE11 support is deprecated.
- View Engine removed and IE11 support dropped (Angular 12 → Angular 13): View Engine is removed from the framework and libraries are now published in Ivy partial-compilation format. Older View Engine libraries still work through ngcc until v16. Internet Explorer 11 support is removed, and string-based loadChildren must use dynamic import().
- Typed Reactive Forms (Angular 13 → Angular 14): FormControl, FormGroup, and FormArray are now strictly typed. Existing forms code may stop compiling; the migration swaps to Untyped* variants so you can adopt typing gradually.
- Angular Material migrates to MDC (Angular 14 → Angular 15): Angular Material components are rebuilt on Material Design Components (MDC). DOM structure and CSS change — audit custom Material styles and run the Material migration. Legacy components are available under @angular/material/legacy-* temporarily.
- ngcc is removed — View Engine libraries no longer work (Angular 15 → Angular 16): The Angular Compatibility Compiler (ngcc) is removed, so any dependency still shipped in View Engine format fails to build. Update or replace those libraries before this hop.
- New esbuild/Vite application builder is the default (Angular 16 → Angular 17): New applications use the esbuild + Vite application builder (@angular-devkit/build-angular:application) with faster builds and a Vite dev server. Existing apps keep the webpack builder until migrated. SSR moves to the new @angular/ssr package and is offered during ng new.
Hops in this path
- Angular 10 → Angular 11 — 5 steps
- Angular 11 → Angular 12 — 5 steps
- Angular 12 → Angular 13 — 5 steps
- Angular 13 → Angular 14 — 5 steps
- Angular 14 → Angular 15 — 5 steps
- Angular 15 → Angular 16 — 6 steps
- Angular 16 → Angular 17 — 6 steps
- Angular 17 → Angular 18 — 5 steps
Before you start
- Commit or stash your work and upgrade on a branch so you can roll back.
- Get on the latest minor/patch of Angular 10 before the first hop.
- Update third-party libraries (including Angular Material/CDK) alongside each hop, and run your tests after each one.
Sources
Every step in this plan is checked against Angular's official documentation and release notes. Last reviewed .
- Angular Update Guide: v10 → v11
- Angular 11.0.0 release notes
- Angular Update Guide: v11 → v12
- Angular 12.0.0 release notes
- Angular Update Guide: v12 → v13
- Angular 13.0.0 release notes
- Angular Update Guide: v13 → v14
- Angular 14.0.0 release notes
- Angular Update Guide: v14 → v15
- Angular 15.0.0 release notes
- Angular Update Guide: v15 → v16
- Angular 16.0.0 release notes
- Angular Update Guide: v16 → v17
- Angular 17.0.0 release notes
- Angular Update Guide: v17 → v18
- Angular 18.0.0 release notes
- Angular version compatibility (Node.js, TypeScript, RxJS)
- Angular Update Guide