-
Notifications
You must be signed in to change notification settings - Fork 12k
ng update does not check or update @angular-devkit packages #13581
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
Comments
Even if you manually update |
just ran into this. npm i @angular-devkit/[email protected] @angular-devkit/[email protected] and all your apps "es5BrowserSupport": true CLI version 7.3.4 |
This should add ng-update support to updating ALL the packages that are published from this repo. Fixes angular#13581
This should add ng-update support to updating ALL the packages that are published from this repo. Fixes angular#13581
This should add ng-update support to updating packages that are published from this repo. The build script only updates package.json's ng-update packageGroup dependencies, so these should be kept up to date in the future (when new packages are created). Fixes angular#13581
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. |
I have angular CLI 7.3.0. According to the release description here, This release also involved releasing
@angular-devkit/build-angular 0.13.0
.As you can see in my screenshot below, I have @angular-devkit/build-angular, @angular-devkit/architect, @angular-devkit/build-optimizer, @angular-devkit/build-webpack all at version 0.10.2.
I then do an
ng update
, and the CLI tells me that everything is in order. Why? Shouldn't it tell me that I need to update all of the previously mentioned packages to 0.13.0?Or better yet, shouldn't those packages automatically update when I do an
ng update @angular/cli
? That is the command I did to update to CLI 7.3.0, and the @Angular-devkit packages did not updateThe text was updated successfully, but these errors were encountered: