fix: ng update showing packages that do not exist in my package #1543
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default if no `packageGroupName` is provided `ng-update` will use the first item in `packageGroup` which in this case it is always `@nguniversal/aspnetcore-engine`. With this change we set the `packageGroupName` of each package, also we remove `ng-update` from `@nguniversal/builders` as this gets updated when running `ng update` on `@nguniversal/express-engine` or `@nguniversal/hapi-engine`. Closes #1542 and closes #1533
alan-agius4
requested review from
CaerusKaru,
kyliau and
MarkPieszak
as code owners
alan-agius4
added
the
target: minor
CaerusKaru
approved these changes
Mar 9, 2020
|
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.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default if no
packageGroupNameis providedng-updatewill use the first item inpackageGroupwhich in this case it is always@nguniversal/aspnetcore-engine.With this change we set the
packageGroupNameof each package, also we removeng-updatefrom@nguniversal/buildersas this gets updated when runningng updateon@nguniversal/express-engineor@nguniversal/hapi-engine.Closes #1542 and closes #1533