This issue impacts 9.0.0-rc.0 and happened while updating https://github.com/vmware/clarity.
In https://next.angular.io/guide/updating-to-version-9 the suggested update procedure is to follow these commands:
npm install --no-save @angular/cli@^8.3.15
ng update @angular/cli @angular/core --next
When the update procedure fails, a user will need to manually revert their repository to before the update (as described in #16020) and attempt to update again.
If the user forgets to run npm install --no-save @angular/cli@^8.3.15, they will end up an incorrect update.
It would be better to instruct users to save and commit their update to @angular/cli@^8.3.15 before proceeding in order to reduce mistakes in subsequent update attempts.
cc @StephenFluin @mgechev
This issue impacts 9.0.0-rc.0 and happened while updating https://github.com/vmware/clarity.
In https://next.angular.io/guide/updating-to-version-9 the suggested update procedure is to follow these commands:
When the update procedure fails, a user will need to manually revert their repository to before the update (as described in #16020) and attempt to update again.
If the user forgets to run
npm install --no-save @angular/cli@^8.3.15, they will end up an incorrect update.It would be better to instruct users to save and commit their update to
@angular/cli@^8.3.15before proceeding in order to reduce mistakes in subsequent update attempts.cc @StephenFluin @mgechev