Closed damyanpetev closed 3 months ago
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
Command
update
Is this a regression?
The previous version in which this bug was not present was
No response
Description
When updating a current project to Angular 18 RC the![image](https://github.com/angular/angular-cli/assets/3198469/e776f73c-84bc-4ab7-8ff0-520eedadcd7f)
ng update
command suggest to update@angular/build
which is new and not present in the project and consecutively fails if attempted.The working command to run is still
ng update @angular/cli --next
instead, but the suggestion is wrong due to the new group name since@angular/build
has been added as first it now shows up as the group name: https://github.com/angular/angular-cli/blob/c79a513a766383a5eac44acfbb8ac3aab10bbfc4/packages/angular/cli/package.json#L45-L47Not sure what the end goal of the new package is, but assuming the CLI is not going away - perhaps move it back up on to the group so the updates still go though it?
Minimal Reproduction
ng new
ng update --next
and inspect listed commendsng update @angular/build --next
as suggestedFirst reproduced here https://github.com/IgniteUI/igniteui-angular/pull/14237 but also tested on a completely fresh app so pretty sure it'll repro on any existing project.
Exception or Error
Your Environment
Anything else relevant?
No response