Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

To keep an Angular project current, check its installed versions with ng version, review available updates with ng update, then follow Angular’s Update Guide for the project’s exact starting and target versions. Update to the latest patch, move between major versions one major at a time, and verify Node.js, TypeScript, and RxJS compatibility before changing dependencies.

Check your project and find the right update path

  1. From your project directory, run ng version to see the installed Angular and Angular CLI versions.

  2. Run ng update to list available updates. For a basic framework and CLI update, Angular documents ng update @angular/cli @angular/core.

    What’s actually slowing this PC down?

    Pick the symptom - the matching free tool is one click away.

    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  3. Open the Angular Update Guide and select your current version, target version, project complexity, and relevant dependencies. The guide can account for dependencies such as Angular Material or ngUpgrade.

  4. Before updating, check the version compatibility table for the target version’s Node.js, TypeScript, and RxJS requirements.

For a multi-major upgrade, take one major step at a time. Angular’s policy allows an ng update step only when the source version is within one major version of the supported target. Use the ng update reference for command options and guidance.

Choose an update target based on support and compatibility

As of Angular’s release-policy snapshot checked October 7, 2026, Angular 22 is in Active support, Angular 21 and 20 are in Long-Term Support (LTS), and versions 2 through 19 are no longer supported. These statuses can change, so check Angular’s release policy when planning an upgrade.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Angular typically supports a major version for 24 months: 12 months of Active support followed by 12 months of LTS. The policy describes approximate dates, which may change. Its stated cadence is one major release every 12 months, four to six minor releases per major, and patch or pre-release builds almost every week. These are policy figures, not independent measurements.

For Angular 22, the compatibility table checked 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. Compatibility ranges are version-specific and may change; recheck the official table before upgrading.

Understand the risk by release type

Before a major update, review the relevant release changes and migrations, then run the project’s tests. Treat the upgrade as project work rather than assuming that changing the package versions is sufficient.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Plan for deprecated APIs

Angular says it announces deprecated APIs in its changelog and documentation, along with a recommended update path. A deprecated API remains available through at least one major release—approximately a year—and removal happens in a major release. The policy notes that exceptional cases, such as critical security patches, may introduce breaking changes with explicit notice.

Check the changelog and documentation for APIs your project uses, and follow the stated migration path before a removal affects a later upgrade.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use official Angular tools and references

The Angular CLI provides commands for working with Angular projects; its purpose and command documentation are available in the CLI overview and CLI reference. For the update itself, use the project-specific guide, the ng update reference, the release policy, and the version compatibility table. Because support and compatibility details are time-sensitive, verify them again when you are ready to upgrade.

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.