-
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
Wrong packages when running ng update #22087
Labels
Milestone
Comments
@ties-s, can you please share your |
|
alan-agius4
added
ng update DX
area: @angular/cli
needs: investigation
Requires some digging to determine if action is needed
labels
Nov 4, 2021
clydin
removed
the
needs: investigation
Requires some digging to determine if action is needed
label
Nov 9, 2021
clydin
pushed a commit
that referenced
this issue
Nov 9, 2021
…tput With this change we favor the `packageGroupName` name when specified and only fallback to use the first item in in the `packageGroup` array when it is not specified. Closes #22087
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which @angular/* package(s) are the source of the bug?
upgrade
Is this a regression?
Yes
Description
When running
ng update
it lists@nguniversal/aspnetcore-engine
while I'm using universal with express only (which isn't listed)Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in
Anything else?
No response
The text was updated successfully, but these errors were encountered: