Open mpsdenis opened 11 months ago
The workaround that works is described in the issue mentioned above - simply manually update @angular/cli
with yarn add @angular/cli
and then run ng update @angular/core
.
And don't forget to run ng generate @angular/core:control-flow
after that for better development experience 😄
Command
update
Is this a regression?
The previous version in which this bug was not present was
V16
Description
This has happened before (https://github.com/angular/angular-cli/issues/19209) and now happens again when trying to upgrade to angular v17.
Tried to install the update with npm to check if yarn is the cause and npm goes through successfully.
Minimal Reproduction
Try to upgrade angular 16 to 17 using yarn v3 (current specific version we're using is
v3.6.4
, but I tried to upgrade yarn tov4.0.2
and it's the same behavior).Global angular/cli is v17, local is v16 (obviously).
Exception or Error
No response
Your Environment
Anything else relevant?
No response