I've upgraded my project to Angular 6, and everything went fine except the conversion of .angular-cli.json file. From the guide I followed, it was said that this will convert it automatically.

npm install -g @angular/cli

npm install @angular/cli

ng update @angular/cli

However, it was not the case as I still have the old .angular-cli.json

Is there a way to do it automatically / manually?

Most likely there were errors in one of those commands. For me, I had to run npm install -g @angular-devkit/core first and then run the commands:

npm install -g @angular/cli

npm install @angular/cli

In the console output of npm install @angular/cli you should see:

The Angular CLI configuration format has been changed, and your existing configuration can
be updated automatically by running the following command:

  ng update @angular/cli

Then you obviously should run ng update @angular/cli to finish off the process.

See the Official Update Guide for additional details.

120 users liked answer #0dislike answer #0120
Kyle Krzeski profile pic
Kyle Krzeski

you can automatically update your existing angular-cli.json file to angular.json file by using the below command provided that you are on v6.x.x or greater of angular cli command line tool.

ng update @angular/cli --from=1.7.4 --to=6 --migrate-only

In the above command 1.7.4 is the previous cli version you were using. The --migrate-only flag makes sure that it will only perform a migration but does not update the installed version. Use --to instead of @angular/cli@6 because of https://github.com/angular/angular-update-guide/issues/64.

read more: angular/cli-github

79 users liked answer #1dislike answer #179
rgantla profile pic

Try running "ng update @angular/cli" twice it will update angular-cli.json to angular.json


if getting errors like this:

ERROR: The specified command update is invalid, for available options see ng-help.

then you need to run 2 commands as follows

  1. npm install --save-dev @angular/cli@latest.
  2. ng update @angular/cli

this will automatically create angular.json, delete .angular-cli.json and update karma.conf.js, src/tsconfig.spec.json, package.json, and tslint.json

42 users liked answer #2dislike answer #242
T. Shashwat profile pic
T. Shashwat

I was trying to update from 5.2 -> 6.1 and was running into an issue where after running npm install @angular/cli@6 followed by ng update @angular/cli@6, (as described by https://update.angular.io/#5.2:6.1) my package.json was being updated but none of the other files like .angular-cli.json or tsconfig.json were, even though I received no errors. I tried executing the update command multiple times but this had no effect.

I ended up running the following 3 commands which worked for me:

npm install @angular/cli@6
ng update @angular/cli
ng update @angular/core@6

The only real change there is the second command. The document says to run ng update @angular/cli@6 but that wouldn't update any of the config files.

22 users liked answer #3dislike answer #322
MacK profile pic

For upgrading version from 5.2 to 6.0 , I followed up the following steps.

  • Install Node 8 or above.
  • yarn global add @angular/cli.
  • yarn add @angular/cli.
  • ng update @angular/cli.
  • ng update @angular/core.

    Note: if, after executing ng update @angular/core command,invalid range issue arises,then follow below, just replace the major version in package.json, it'll automatically replace the minor. Resource : Want to upgrade project from Angular v5 to Angular v6

      - npm uninstall -g angular-cli
      - npm cache clean or npm cache verify
      - npm install -g @angular/cli@next
      - then, replace lower versions to higher versions in package.json 
      - delete node modules folder.
      - run npm/yarn install.

After npm install, if you get error of missing src/styles path, then remove the paths given in angular.json file under assets block from ["src/styles", "src/fonts", "src/images", "src/assets", "src/favicon.ico"] to ["assets","favicon.ico"].

  • yarn global add rxjs-tslint (might required).
  • rxjs-5-to-6-migrate -p src/tsconfig.app.json (might required).
  • yarn install @angular/material@6.0.0 (to update material packages).

=> Please note you never need to rename angular.cli.json to angular.json manually!!

** feel free to ask if further queries arises.

3 users liked answer #4dislike answer #43
Simran kaur profile pic
Simran kaur

Please follow these steps :

1) Update your Angular CLI globally and locally (assuming latest version to be 7)

2) Take your old project and run following command

  • npm install @angular/cli
  • ng update @angular/cli

After running this you have updated all your angular packages to the latest version.

3)Add this package as it is still missing

npm install @angular-devkit/core --save -dev

4) create a fresh new project with ng serve (latest version)

5) Create a new empty file with name angular.json and copy the content of angular.json from the new project into it.

6) Update the name of project accordingly in angular.json

7) Run npm install

8) Run ng serve

9) You are now ready with the latest version of angular.

I followed the above steps to migrate from angular2 to angular7.

1 users liked answer #5dislike answer #51
Sourabh Ranka profile pic
Sourabh Ranka

Local workspace file ('angular.json') could not be found.
The serve command requires to be run in an Angular project, but a project definition could not be found.

Upgrade/downgrade to the desired version ( I tried Angular 6 for example )

[sudo] npm install -g -f @angular/cli@6.1.4

Update the local project

ng update @angular/cli@6.1.4

And you're good to go :)

ng serve
0 users liked answer #6dislike answer #60
Bogdan Iudean profile pic
Bogdan Iudean

I had to actually commit every changes or stash them before I could run the command to update the cli as shown in this screenshot.

I did these commands:

npm install --save-dev @angular/cli@latest 

ng update@angular/cli

And committing the changes between these two.

0 users liked answer #7dislike answer #70
Tore Aurstad profile pic
Tore Aurstad

Copyright © 2022 QueryThreads

All content on Query Threads is licensed under the Creative Commons Attribution-ShareAlike 3.0 license (CC BY-SA 3.0).