Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallTo update Angular safely, check the project’s current versions, choose the correct source-to-target path in Angular’s interactive Update Guide, and apply the CLI-recommended changes. If the target is several major versions ahead, update one major at a time; for each step, use the latest patch in that major and follow the guide’s migration instructions.
Check the project and its available updates
Run these commands from the Angular project directory. The first reports the versions installed in the workspace; the second shows updates the CLI considers available for that project.
As an Amazon Associate I earn from qualifying purchases.
ng version
ng updateBefore changing dependencies, review the repository state and make sure you have a way to recover your work. Angular CLI’s allow-dirty option defaults to false, so the CLI normally will not update a workspace with uncommitted changes. The CLI also documents a create-commits option for creating commits during an update; neither option replaces your own source-control and recovery practices. See Angular’s CLI update reference.
Choose the right update path
Open Angular’s interactive Update Guide and select the installed source version and intended target version. Then choose the project complexity—Basic, Medium, or Advanced—and any relevant options, including Angular Material, ngUpgrade, or Windows. The instructions depend on those choices, so review the full generated path, including manual changes and troubleshooting notes.
#1 Best Overall
Simple update within a major version
For a straightforward update, the CLI may be sufficient. Angular’s general command for updating the core framework and CLI is:
ng update @angular/cli @angular/coreUse the Update Guide if you are unsure whether the project has additional migration steps or dependencies that affect this path.
Update to a specific major version
When targeting a major release, use the major-version package syntax documented by the CLI, substituting the intended major version:
Recommended Free Tools
ng update @angular/cli@^<major> @angular/core@^<major>For example, replace <major> with the target major number. Choose the latest patch in that major rather than the initial major release: Angular recommends this because later patches include fixes released since the major’s initial release. Confirm the exact path in the Update Guide before running the command.
Rank #3
Move through multiple major versions one at a time
Do not jump directly across several major releases. Angular’s supported update guidance is to move one major version at a time, applying that version’s migrations and checking its guide before proceeding to the next. For example, a move from Angular 10 to 12 follows the 10-to-11 path first, then the 11-to-12 path. Check that each intermediate version is supported for the update path you are taking.
Check Angular support status before choosing a target
Angular versions major.minor.patch identify the release line and patch level. Angular describes minor releases as backward-compatible, while major releases can bring significant changes and may require developer work. Patch releases are intended for bug fixes, and Angular recommends using the latest patch in the target major.
Angular’s release policy describes a typical major-release cadence of 12 months, 4–6 minor releases per major, and patch or pre-release builds almost every week. Major versions are typically supported for 24 months: 12 months of Active support followed by 12 months of Long-term support.
The live support table lists Angular 22 as Active, Angular 21 as LTS, and Angular 20 as LTS; it lists Angular 2 through 19 as unsupported. These statuses change over time, so check the current table before choosing a destination. A version being newer does not, by itself, establish that it is supported.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Account for third-party libraries
Angular applications often depend on packages beyond the framework and CLI. Use ng update to check for library updates, then review the libraries’ peer dependencies and any migration instructions from their maintainers. Some packages depend on one another, so they may need to be updated in a deliberate order. Angular explains this in its guide to using libraries.
Apply migrations and verify the application
Follow the guide’s manual steps as well as the CLI’s generated migrations. A major update can involve refactoring or learning changed APIs, so run the build and the tests relevant to your application after completing the changes. The exact verification plan depends on the project; Angular’s release guidance notes that major updates may require additional testing and refactoring.
When not to force an update
The CLI provides a --force option that ignores peer-dependency mismatches. Ignoring a mismatch does not make the packages compatible, so do not use it as a routine way to get past an update failure. Investigate which package has the conflicting peer requirement, consult its compatibility guidance, and choose an update order or target version that satisfies the dependencies.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
