Angular 22, current ng-bootstrap 21, npm audit fx

Author: FritzHerbersCreated Jun 18, 2026Updated Jun 18, 2026

Noticed the following behavior with npm audit fix, that the old ng-bootstrap v5.3.1 is installed.

npm audit fix --force npm warn using --force Recommended protections disabled. npm warn Unknown user config "python". This will stop working in the next major version of npm. See npm help npmrc for supported config options. npm warn audit No fix available for @angular/build@<=22.0.2 npm warn audit Updating @ng-bootstrap/ng-bootstrap to 5.3.1, which is a SemVer major change. npm warn audit Updating @ng-bootstrap/ng-bootstrap to 5.3.1, which is a SemVer major change. npm warn ERESOLVE overriding peer dependency npm warn While resolving: @angular/[email protected] npm warn Found: @angular/[email protected] npm warn node_modules/@angular/compiler-cli npm warn dev @angular/compiler-cli@"^15.0.4" from the root project npm warn npm warn Could not resolve dependency: npm warn peer @angular/compiler-cli@"^22.0.0" from @angular/[email protected] npm warn node_modules/@angular/build npm warn dev @angular/build@"^22.0.2" from the root project

I use npm audit fix --force regularly and haven't noticed this behavior before.

Using

  • Angular v22.0.2
  • ng-bootstrap v21 (lastest version as per package.json)

Source: ng-bootstrap/ng-bootstrap