How to Check Angular Version using Command Line

To check an Angular version, go inside the recently created Angular project and use the “ng version” command.

ng version


Check Angular Version using Command Line

The ng version outputs the Angular CLI version.

You can see that I am using Angular CLI version 16.1.6.

Besides that, we can see all the library’s versions shipped with Angular and rxjs, typescript, and webpack.

You can also check the version of Angular CLI without going into the project folder, but in that instance, sometimes, the Angular version is undefined or empty.

Let’s say I am in my root folder of the system and hit the ng version command, and then I will get the following output.


If you have already created an angular project or an old one using Angular CLI, go inside that folder and type the ng version command.

To check the version of Angular CLI, you don’t need to go inside any Angular project, but if you’re going to check the version of Angular, you should go inside that project folder and then type the command. It will give you some extra information about other package versions as well.

You can also type the ng –version command to check the Angular or Angular CLI version.

Two ways to check the Angular Version ProjectWise

  1. Open the Terminal inside your project and type ngversion. This will list the versions of several Angular packages installed in your project for recent Angular versions.
  2. Open the package.json file and examine the Angular packages referenced in your project.

Angular versioning

Angular version numbers designate the level of changes introduced by the release. This use of semantic versioning supports you in understanding the potential significance of updating to a new version.

Angular version numbers have three parts: major.minor.patch.

For example, version 10.3.9 indicates major version 10, minor version 3, and patch level 9.

The version number is incremented based on the level of modification included in the release.

  1. Major releases contain important new features, but minimal developer support is expected during an update. When updating the latest major release, you may need to run commands like update scripts, refactor code, run additional tests, and learn new APIs.
  2. Minor releases include the new smaller features. Minor releases are fully backward-compatible; no developer assistance is required during the updates, but you can optionally change your apps and libraries to begin using new APIs, features, and abilities added. We update peer dependencies in minor versions by extending the supported versions, but we do not require projects to update those dependencies.
  3. Patch releases are low-risk, bug-fix releases. Therefore, no developer assistance is required during the update.

New Angular Version release frequency

In general, you can assume the following release cycle:

  1. A major release every six months.
  2. 1-3 minor releases for each major release.
  3. A patch release and pre-release (next or rc) build almost every week.

All of our major releases are supported for 18 months.

  1. 6 months of active support, during which the core team releases regularly scheduled updates and patches.
  2. 12 months of long-term support (LTS), during which the angular core team of developers releases only critical fixes and security patches.

That’s it!

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.