I try update Angular project from version 7.2.5 to 8 of the core framework and CLI by running ng update @angular/cli @angular/core
in terminal.
Response from terminal was 'We analyzed your package.json and everything seems to be in order. Good work!'
My version list:
$ ng version
_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 7.3.9
Node: 11.14.0
OS: darwin x64
Angular: 7.2.15
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
Package Version
------------------------------------------------------------
@angular-devkit/architect 0.13.9
@angular-devkit/build-angular 0.13.9
@angular-devkit/build-ng-packagr 0.13.9
@angular-devkit/build-optimizer 0.13.9
@angular-devkit/build-webpack 0.13.9
@angular-devkit/core 7.3.9
@angular-devkit/schematics 7.3.9
@angular/cdk 7.3.7
@angular/cli 7.3.9
@angular/material 7.3.7
@ngtools/json-schema 1.1.0
@ngtools/webpack 7.3.9
@schematics/angular 7.3.9 (cli-only)
@schematics/update 0.13.9
ng-packagr 5.2.0
rxjs 6.5.2
typescript 3.2.4
webpack 4.29.0
As of today it is alread stable 8.0.0
:)
You might want to try to run ng update --all
to update all packages in your package.json
file.
That might, however, not proceed if it discovers that some inter-dependencies are not met among other packages.
In such a case you might want to also add --force
option.
Alternatively, you can choose a more tailored approach and hand-pick packages to update (as suggested in answer by Veeraragavan), but you no longer need to add @next
version, since all Angular package 8.0.0 versions are stable as of now.