Let’s suppose we have to update our Angular version i.e. for security reasons / new features. However, some of your libraries can still use outdated Angular version.
As an example we’ll consider the following Angular (already updated) modules’ versions:
my-app => package.json
"dependencies": {
    "@angular/common": "^14.2.0",
    "@angular/core": "^14.2.0",
    ...
    ...
}While our lib contains constraints to have the following versions:
my-awesome-lib => package.json
"peerDependencies": {
    "@angular/common": "^13.3.12",
    "@angular/core": "^13.3.12"
  }In order to deal with this problem we can:
- Wait & block our work till our 
my-awesome-libsupports Angular components in v.^14.2.0👎 Overridethese deps => enforce using versions we provide for the lib 🤩
In order to override our my-awesome-lib we’ll need to include overrides object, with following possible configurations:
"overrides": {
    "my-awesome-lib": {
      "@angular/common": "14.2.0",
      "@angular/core": "14.2.0"
    }
  }"overrides": {
    "my-awesome-lib": {
      "@angular/common": "^14.2.0",
      "@angular/core": "^14.2.0"
    }
  }"overrides": {
    "my-awesome-lib": {
      "@angular/common": "$@angular/common",
      "@angular/core": "$@angular/core"
    }
  }