To keep an Angular project current, check its installed versions with ng version, review available updates with ng update, and follow the Angular Update Guide for the exact path from your current version to the target. Update one major version at a time, use the latest patch release, confirm Node.js, TypeScript, and RxJS compatibility, then run your project’s tests.
Check your project and available updates
-
From the project directory, run
ng versionto see the installed Angular and Angular CLI versions.As an Amazon Associate I earn from qualifying purchases.
-
Run
ng updateto see the updates available for that project.Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
For a basic framework and CLI update, Angular documents
ng update @angular/cli @angular/core. Angular recommends using the latest patch release because it includes fixes released after the initial major version. See the Angular CLI update reference.#1 Best Overall
Choose the right update path
Before changing dependencies, open the Angular Update Guide and select your source version, target version, project complexity, and relevant dependencies. This tailors the migration steps to your project, including dependencies such as Angular Material or ngUpgrade.
For a multi-major upgrade, move one major version at a time. Angular’s release policy allows an ng update step when the source version is within one major version of the supported target. Use the guide for each step rather than skipping directly across several majors.
Verify runtime and package compatibility
Check the Angular version compatibility table before installing a target version. It lists the supported Node.js, TypeScript, and RxJS ranges; a project’s existing environment may need to change before the Angular update can proceed.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesFor Angular 22, the table checked on October 7, 2026 lists Node.js ^22.22.3 || ^24.15.0 || ^26.0.0, TypeScript >=6.0.0 <6.1.0, and RxJS ^6.5.3 || ^7.4.0. These ranges can change, so verify them in the live compatibility table when planning an upgrade.
Know what kind of change to expect
-
Major releases can introduce significant features and migration work. Review the release changes and any migrations; the work may involve scripts, refactoring, additional tests, or learning new APIs.
-
Minor releases are backward-compatible under Angular’s release policy.
-
Patch releases are described as low-risk bug fixes. Prefer the latest patch for your selected major version.
Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Angular’s policy describes a cadence of one major release every 12 months, 4–6 minor releases per major, and patch or pre-release builds almost every week. These are policy figures, not a guarantee of a particular release date. The versioning and releases page is the authoritative place to check current policy and release information.
Check Angular’s support status
As of October 7, 2026, Angular lists v22 as Active and v21 and v20 as LTS; v2 through v19 are no longer supported. Angular’s typical support period is 24 months: 12 months of Active support followed by 12 months of LTS. The schedule is approximate and may change, so confirm the current status on Angular’s release page before deciding which version to target.
Account for deprecated APIs and test the migration
Angular says it announces deprecated APIs in its changelog and documentation with a recommended update path. A deprecated API remains for at least one major release, with removals occurring in a major release. The policy also allows exceptional breaking changes, such as those needed for critical security patches, with explicit notice.
After updating, review the migration output and release changes, then run the project’s tests. Major updates can require changes beyond package installation, so treat them as migration work rather than assuming that a successful command means the application is ready.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →A practical update checklist
-
Record the installed Angular and CLI versions using
ng version. -
Inspect available updates with
ng updateand consult the Update Guide for your project’s source-to-target path. -
For a major-version change, take one major step at a time and select the latest patch in that major.
-
Verify Node.js, TypeScript, and RxJS compatibility for the target.
Free tools Windows power users keep installed
One-click scans. No signup required.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Review migrations and release changes, then run the project’s tests.
Quick Recap
SaleBestseller No. 1SaleBestseller No. 3Bestseller No. 4
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.
