Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: ng update showing packages that do not exist in my package #1543

Merged
merged 1 commit into from
Mar 9, 2020
Merged

fix: ng update showing packages that do not exist in my package #1543

merged 1 commit into from
Mar 9, 2020

Commits on Mar 9, 2020

  1. fix: ng update showing packages that do not exist in my package 

    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
    alan-agius4 committed Mar 9, 2020
    Configuration menu
    Copy the full SHA
    25628c8 View commit details
    Browse the repository at this point in the history