Support wildcards in update

[geo242]

🚀 Feature request

• [ ] new
• [ ] build
• [ ] serve
• [ ] test
• [ ] e2e
• [ ] generate
• [ ] add
• [x] update
• [ ] lint
• [ ] extract-i18n
• [ ] run
• [ ] config
• [ ] help
• [ ] version
• [ ] doc

Description

It would be nice to be able to update multiple packages without typing them all out. For example:

ng update @angular-eslint/* would update @angular-eslint/schematics and @angular-eslint/eslint-plugin and so on.

and

ng update @progress/kendo-angular* would update all kendo angular packages.

Describe the solution you'd like

See Description

Describe alternatives you've considered

There are no alternatives that I am aware of.

[angular-robot[bot]]

This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list.

You can find more details about the feature request process in our documentation.

[angular-robot[bot]]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot[bot]]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

[egonknapen]

I like to upvote this issue too. And personally I think 20 days for voting is a bit ridiculously short. I have been having this issue for a very long time. Only today, I thought about issuing feature request for it. Of course I didn't find anything when searching for it, but thank @alan-agius4 for pointing me out to this feature request. Which is even better than my request.

Probably need a new feature request for voting in general. Why not just leave voting open. And when 1 year later, there are enough people interested in it, the core team can have a look at it again?

[geo242]

@egonknapen They originally gave 60 days, but regardless, I agree that they should just keep it open. I am not an "influencer", and it's not like anyone ever comes to this corner of the web unless they are having a specific issue. So, it's completely unfair to just deny something on this basis.

[alan-agius4]

This is already possible without the need for the wildcard, however this needs to be configured by the library author as they'd need to defined packageGroup example https://github.com/angular/angular-cli/blob/cff766326a886e96e65406036af9f3fdaa4a2920/packages/angular/cli/package.json#L44-L55

Which when running ng update would cause all the listed packages and their peer dependencies to also be updated.

Example: when you run ng update @angular/core all the @angular/ dependencies are updated and you don't need to run update for every single package.