How many steps does the Angular 12 to Angular 13 upgrade involve?

This path spans 1 version hop with 5 planned steps across pre-flight, requirements, ng update, breaking changes, deprecations, and migrations.

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

From (current version)

To (target version)

Angular 12 → Angular 130 of 5 done · 1 hop

Angular 12 → Angular 13

(5 steps)

Commit a clean tree and update to the latest minor firstPre-flight

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.

Requires Node 12.20+/14.15+/16.10+ and TypeScript 4.4Tooling / Requirements

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 →

Run ng update to Angular 13Update Command

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 removed and IE11 support droppedBreaking Change

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 generic required; entryComponents removedDeprecation / Removal

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

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 12 to Angular 13

This plan covers the full path from Angular 12 to Angular 13 — 1 version hop and 5 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 12 and Angular 13

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().

Hops in this path

Angular 12 → Angular 13 — 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 12 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 September 28, 2026.