Expected behavior When we are working with angular 11, we have an issue regarding incompatibilities with your peer dependencies. when we change it manually from node_module then it will be fine, but every time we need to change node_module's peerDependencies for your package. or embed it into other package. so both of them are not good solution. Actual behavior Upgrade to angular 11 for your main branch or at least set your peerDependencies to angular 11 in other branch that we can use it. Resources (screenshots, code snippets etc.)

{
  "name": "ng-uikit-pro-standard",
  "version": "11.0.0",
  "files": [
    "assets/**/*",
    "bundles/**/*",
    "esm5/**/*",
    "esm2015/**/*",
    "fesm5/**/*",
    "fesm2015/**/*",
    "lib/**/*",
    "schematics/**/*",
    ".gitignore",
    "changelog",
    "license.pdf",
    "ng-uikit-pro-standard.d.ts",
    "ng-uikit-pro-standard.metadata.json",
    "package.json",
    "public_api.d.ts"
  ],
  "dependencies": {
    "tslib": "^2.0.3"
  },
  "peerDependencies": {
    "@angular/common": "~11.0.0", /* it was 10, I changed manually then it is working */
    "@angular/core": "~11.0.0",
    "@angular/animations": "~11.0.0",
    "@angular/forms": "~11.0.0",
    "@angular/cdk": "^11.0.0"
  },
  "schematics": "./schematics/collection.json",
  "ng-update": {
    "migrations": "./schematics/migration.json"
  },
  "main": "bundles/ng-uikit-pro-standard.umd.js",
  "module": "fesm5/ng-uikit-pro-standard.js",
  "es2015": "fesm2015/ng-uikit-pro-standard.js",
  "esm5": "esm5/ng-uikit-pro-standard.js",
  "esm2015": "esm2015/ng-uikit-pro-standard.js",
  "fesm5": "fesm5/ng-uikit-pro-standard.js",
  "fesm2015": "fesm2015/ng-uikit-pro-standard.js",
  "typings": "ng-uikit-pro-standard.d.ts",
  "metadata": "ng-uikit-pro-standard.metadata.json",
  "sideEffects": false
}