-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring back ng update --all
(includes: workaround with jq
)
#23261
Comments
Hi @SamuelMarks, Thanks for this request. In many cases we found that the This option also contradicted our recommendation, which is to avoid updating multiple packages at once especially across major versions. For the time being this is not something that we are actively looking in bring back. We can re-consider this in the future if there is a greater interest from the community as such I am going to mark this as a feature request. |
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. |
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. |
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. |
Hi @SamuelMarks, Thanks for this feature request, however this is currently out of scope. Let's re-consider this in the future if there is a larger demand for this. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🚀 Feature request
Command (mark with an
x
)Description
Describe the solution you'd like
Bring back
--all
… maybe with a-f
/--force
so the warning can remain.Describe alternatives you've considered
ng update --force $(jq -r '.dependencies * .devDependencies | keys | map(select(startswith("@angular"))) | @tsv' package.json)
(then run:
ncu
-ux '/typescript|rxjs/'
)The text was updated successfully, but these errors were encountered: