You have to be inside an angular-cli project in order to use the build command after reinstall of angular-cli

Question

I had the latest angular-cli installed globally and my project was building successfully.

While reading a suggested solution for another issue, (https://github.com/angular/angular-cli/issues/917) I uninstalled the global angular-cli and installed it as a dev-dependency.

That other issue wasn't solved so I uninstalled the dev-dependency and reinstalled angular-cli globally once again. Now when I try to do an ng build I'm getting the error:

You have to be inside an angular-cli project in order to use the build command

My angular-cli version did not change. Why isn't my project being recognised as an angular-cli project??

In my case, I had to update `@angular/cli` from 1.6.7 to 1.6.8 — JPNotADragon, Oct 27 '18 at 13:00

score 186 · Answer 1 · answered Feb 25 '17 at 19:49

186

Same as John Pankowicz answer, but in my case I had to run

npm install -g @angular/cli@latest

for the versions to match.

answered Feb 25 '17 at 19:49

Oswaldo Salazar

1,968
2
8
4

7

It turns out "@angular/cli" is newer version of "angular-cli". The latter one is globally installed on my system and the former one is listed in package.json. After I replaced the package, it worked. – simonxy May 18 '17 at 06:04
For me, only running the command npm install -g @angular/cli resolved the issue. – DILIP KOSURI May 06 '18 at 11:26
Yeah it Worked! – Naveed Aheer Sep 28 '18 at 11:55
This worked for me as well. It was important for the project I was given to have matching versions – Keenan Payne Oct 18 '18 at 18:03
I was in WebAPI folder, so I had to switch to Angular CLI folder :) – Varun Maggo Jan 18 '19 at 08:47

score 59 · Answer 2 · edited Jun 07 '17 at 20:14

59

npm uninstall -g angular-cli @angular/cli
npm cache clean
npm install -g @angular/cli

use sudo on Mac/Linux.

edited Jun 07 '17 at 20:14

Floern

33,559
24
104
119

answered Jun 07 '17 at 20:12

Vinayaka

591
4
2

npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. – obeliksz Feb 21 '18 at 07:47
If you face this issue: Could not find module "@angular-devkit/build-angular" from.... Then, it might be useful to run as well: npm install --save-dev @angular-devkit/build-angular – Mario Nov 07 '18 at 16:29
1

for 2nd step use --force e.g `npm cache clean --force` – Usman Saleh Jan 20 '20 at 06:57
This was the only thing that worked for me. Thanks! – Andrew Howard Jul 30 '20 at 15:35

score 53 · Accepted Answer · answered Aug 24 '16 at 23:17

53

Ok, found it.

package.json must contain a dependency to angular-cli.

When I uninstalled my local angular-cli, npm also removed the dependency entry.

answered Aug 24 '16 at 23:17

grim_i_am

3,664
5
19
19

8

could you explain with more detail that part about the dependency? – Progs Feb 17 '17 at 19:14
Uninstalling angular-cli as a dev dependency, ie [ npm uninstall --save-dev angular-cli ] removed an entry from the packages.json "devDependencies": { "@angular/cli": "^1.0.0", "..." } and therefore you need to ensure that this entry is available under "devDependencies" or even "dependencies" if necessary – jabu.hlong May 15 '17 at 12:05
So what you did? what exactly you uninstalled? -g or --save? – Janatbek Orozaly Jul 10 '17 at 20:50

score 34 · Answer 4 · edited Nov 19 '18 at 18:24

34

It worked in my case

sudo npm uninstall -g angular-cli @angular/cli
sudo npm cache clean --force
npm install npm@latest -g
sudo npm install -g @angular/cli

edited Nov 19 '18 at 18:24

Diego Venâncio

5,698
2
49
68

answered Nov 05 '17 at 16:59

Humble Freak

459
5
10

2

`npm install npm@latest -g` may not be necessary – Devin Feb 14 '19 at 23:08
Thank you! This fixed it for me :) – CodeMusic Apr 06 '21 at 19:30

score 26 · Answer 5 · answered Feb 24 '17 at 18:47

26

I had the same error message. But the cause and solution are slightly different. When I ran "ng -v" it showed different versions for angular-cli (1.0.0-beta.28.3) and @angular/cli (1.0.0-beta.31). I re-ran:

npm install -g @angular/cli

Now both show a version of 1.0.0-beta.31. The error message is gone and "ng serve" now works. (Yes - it was @angular/cli that I re-installed and the angular-cli version was updated.)

answered Feb 24 '17 at 18:47

John Pankowicz

4,203
2
29
47

Note that it takes a _very_ long time to refresh angular-cli, even an hour. In the middle of a time-critical task it may doom your project. – Tamás Polgár May 29 '17 at 21:14
For me I was trying npm install -g angular-cli, which is now deprecated. I had to npm install -g @angular/cli – Robbie Smith Nov 09 '17 at 21:34

score 15 · Answer 6 · answered Feb 22 '17 at 02:07

15

Use npm install angular-cli --save-dev

answered Feb 22 '17 at 02:07

Pedro Henrique

151
1
4

6

P.S This is now deprecated... angular-cli has officially moved to `@angular/cli` – shramee Mar 29 '17 at 10:47
Even it was deprecated fixed my issue. Cheers mate. – Gabriel Muñumel Apr 01 '17 at 09:31

score 15 · Answer 7 · edited Jul 15 '19 at 05:30

15

Execute following commands step by step :

sudo npm uninstall -g angular-cli @angular/cli

sudo npm cache clean

npm install npm@latest -g

sudo npm install -g @angular/cli

npm rebuild node-sass --force

edited Jul 15 '19 at 05:30

Prashant Pimpale

10,349
9
44
84

answered Feb 06 '18 at 13:40

Mitesh Panchal

151
1
4

score 11 · Answer 8 · edited Jul 15 '19 at 05:30

11

This is what helped me when I found myself in the same problem:

npm uninstall -g angular-cli @angular/cli
npm cache clean --force
npm install -g @angular/cli@latest

edited Jul 15 '19 at 05:30

Prashant Pimpale

10,349
9
44
84

answered Sep 11 '18 at 09:23

sikaili99

532
6
14

score 5 · Answer 9 · answered May 05 '17 at 05:14

5

npm uninstall -g angular-cli
npm uninstall --save angular-cli
npm uninstall -g @angular/cli
npm uninstall --save @angular/cli
npm cache clean
npm install --save-dev @angular/cli@latest

answered May 05 '17 at 05:14

jhoanna

1,797
25
25

Alex Nevidomsky · Answer 10 · 2017-06-21T17:50:26.097

5

In my case (Mac OS X and previously used Angular 1.5 environment)

npm -g cache clean --force

npm cache clean --force

worked. (npm install -g @angular/cli@latest afterwards)

edited Jun 21 '17 at 17:50

answered Jun 04 '17 at 14:07

Alex Nevidomsky

668
7
14

score 5 · Answer 11 · answered Feb 21 '18 at 11:11

5

It works with npm install -g @angular/cli@latest for me.

answered Feb 21 '18 at 11:11

UmaShankar

221
5
14

score 2 · Answer 12 · answered Jun 28 '18 at 18:53

2

This error comes when there's incompatibility between node version and angular/cli version. therefore use below command to update the cli version to latest

npm install -g @angular/cli@latest

answered Jun 28 '18 at 18:53

Sunali Bandara

402
4
6

score 2 · Answer 13 · edited Jun 06 '19 at 07:57

2

npm uninstall -g angular-cli @angular/cli

npm cache clean --force

npm install -g @angular-cli/latest

I had tried similar commands and work for me but make sure you use them from the command prompt with administrator rights

edited Jun 06 '19 at 07:57

giser_yugang

6,058
4
21
44

answered Jun 06 '19 at 07:53

Onkar Nirhali

216
2
8

score 1 · Answer 14 · answered Nov 22 '17 at 14:45

1

I had the same issue - it turned out that i was using a deprecated angular-cli instead of @angular/cli. The latter was used by my dev team and it took me some time to notice that we were using a different versions of angular-cli.

answered Nov 22 '17 at 14:45

Mac Keicam

11
1

Sanjay Kumar N S · Answer 15 · 2019-02-14T08:57:00.630

1

Just include this in the package.json in devDependencies section

"angular-cli": "1.0.0-beta.25.5"

Not compulsory to install it if you have another vresion of cli installed globally.

I got this issue when I worked with angular2 & 4 at a time with different project. So angular4 - need angular-cli@latest and angular2 need angular-cli the above version.

edited Feb 14 '19 at 08:57

answered Feb 23 '18 at 11:27

Sanjay Kumar N S

4,653
4
23
38

score 1 · Answer 16 · answered Apr 10 '19 at 08:15

1

I faced the same issue while running my project: I found out that if your project is using specific version of any thing in package.json find out that and install the specific version of that dependencies like for me, npm install @angular/cli@^4.0.0.

answered Apr 10 '19 at 08:15

Rutvik Joshi

97
3
13

score 1 · Answer 17 · answered May 25 '20 at 04:46

1

It might be the problem with your version.

npm install -g @angular/cli@latest

The above run worked for me. Thanks!

answered May 25 '20 at 04:46

Jaya Sundeep

99
1
2

score 0 · Answer 18 · edited Dec 25 '17 at 23:16

0

Dont forget of to use --force:

npm cache clean --force

edited Dec 25 '17 at 23:16

Paul Roub

36,322
27
84
93

answered Dec 25 '17 at 22:24

Diego Venâncio

5,698
2
49
68

score 0 · Answer 19 · edited Sep 24 '18 at 06:48

I had the similar problem and nothing was working out but then I Followed below Steps and It worked for me. when I ran cmd as administrator it worked fine for me.

First run the Command Prompt as administrator ans.
Create the new project.

If it still doesn't create the project, remove the folder and all it's files, and then run ng new <project name> followed by ng serve.

If nothing works just uninstall node and every other file related to it and follow the steps above

score 0 · Answer 20 · edited May 22 '19 at 08:54

0

npm uninstall -g angular-cli 

npm install -g @angular/cli

That's it!

enter image description here

edited May 22 '19 at 08:54

vezunchik

3,669
3
16
25

answered May 22 '19 at 08:49

Bhavya Shah

35
3

1

Welcome to Stack Overflow! Please add code and data as text ([using code formatting](//stackoverflow.com/editing-help#code)), not images. Images: A) don't allow us to copy-&-paste the code/errors/data for testing; B) don't permit searching based on the code/error/data contents; and [many more reasons](//meta.stackoverflow.com/a/285557). In general, code/errors/data in text format >>>> code/errors/data as an image >> nothing. Images should only be used, in addition to text in code format, if having the image adds something significant that is not conveyed by just the text code/error/data. – double-beep May 22 '19 at 10:44
Thank you for welcoming me. I will take care of it next time. – Bhavya Shah Jul 31 '20 at 06:46

You have to be inside an angular-cli project in order to use the build command after reinstall of angular-cli

20 Answers20

Linked