projects with @nguniversal/builders fail to update to v17-rc without --force #26167
Description
Command
update
Is this a regression?
- Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
trying with ng update @angular/cli --next without --force will fail
either mention that in https://update.angular.io/?v=16.0-17.0 that if you use @nguniversal/builders you need to use force
or update the code to treat @nguniversal/builders as special case since it's will be replace in the migration steps
Minimal Reproduction
- generate new angular 16 project
- add @nguniversal/express-engine to it
- update to version 17
Exception or Error
Package "@nguniversal/builders" has an incompatible peer dependency to "@angular-devkit/build-angular" (requires "^16.0.0 || ^16.1.0-next.0", would install "17.0.0-rc.2").
× Migration failed: Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.
See "C:\Users\rober\AppData\Local\Temp\ng-Lo6jIx\angular-errors.log" for further details.
Your Environment
Angular CLI: 16.2.8
Node: 18.16.0
Package Manager: npm 9.6.7
OS: win32 x64
Angular: 16.2.11
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1602.8
@angular-devkit/build-angular 16.2.8
@angular-devkit/core 16.2.8
@angular-devkit/schematics 16.2.8
@angular/cli 16.2.8
@nguniversal/builders 16.2.0
@nguniversal/express-engine 16.2.0
@schematics/angular 16.2.8
rxjs 7.8.1
typescript 5.1.6
zone.js 0.13.3
Anything else relevant?
No response