Message "the term 'ng' is not recognized as the name of a cmdlet"

Question

Today, while working through some basic AngularJS introduction, I ran into a problem.

I opened PowerShell to get going on the project. NPM worked.

I was able to install Angular using:

npm install -g @angular/cli

Anytime I tried to run ng, I would get:

the term 'ng' is not recognized as the name of a cmdlet

I tried everything here to no avail. I also had to run `npm install -g @angular/cli` and then it worked. — Jnr, Jul 09 '20 at 06:42
Is it really AngularJS you are using? In 2017 you probably used Angular (without JS). — LosManos, Oct 19 '20 at 09:07

score 172 · Accepted Answer · edited Jul 16 '19 at 20:36

172

The first path in the path variable needs to be the NPM path. Opening the Node.js command prompt I found that the ng command worked there. I dug into the shortcut and found that it references a command to ensure the first Path variable is NPM. To Fix:

Right Clicked on My Computer (windows)
Selected Advanced System Settings
Clicked "Environment Variables"
Under "Path" variable, made the FIRST value listed %AppData%\npm

Once I did that I was able to close powershell and reopen and all worked.

edited Jul 16 '19 at 20:36

Anand

9,201
4
54
73

answered Jul 06 '17 at 21:08

jonrsharpe

107,083
22
201
376

After following above steps "ng -v" working but "ng build" not working. It is giving this error "You seem to not be depending on "@angular/core". This is an error." – PSR Oct 02 '19 at 11:49
30

You can also skip all of this in many cases by just typing "npm run ng...." Npm still usually works in powershell without alteration and 'npm run' will allow you to use ng commands. – SmoveBB Mar 26 '20 at 21:12
It worked for me . I just want to understand why we are getting tis error after installing nodejs which is already in path. – Saroj Kumar Sahoo Apr 26 '20 at 05:56
Hi , It didn't worked for me ..if anybody can help me on skype or zoom please.....i am trying from couple of days but not able to solve...Please – Laxminarayan Charan Aug 28 '20 at 15:03
3

@LaxminarayanCharan *"if anybody can help me on skype or zoom"* is not an appropriate request for SO. If you have a specific problem applying the information that's already available on this site, ask a new question with a [mre]. – jonrsharpe Aug 28 '20 at 15:04
very first you have to run powershell command Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser second we have to run ng.ps1 using powershell ISE – Anish Sinha Apr 21 '21 at 03:31
I did this and now I am pass the not a cmdlet or function error. But now I get, "ng cannot be loaded because running scripts is disabled on this system. – Sam May 28 '21 at 20:35
1

@Sam that's not specific to the Angular CLI, see e.g. https://stackoverflow.com/q/64633727/3001761 (or the comment above yours, by the look of it). – jonrsharpe May 28 '21 at 20:37
@jonrsharpe yes I had to run SetExecutionpolicy RemoteSigned – Sam May 29 '21 at 13:55
This saved my life. Last time setting 'Set-ExecutionPolicy RemoteSigned' worked for me. This time it did not. Setting the path worked this time. – Sam Jun 26 '21 at 21:49

score 149 · Answer 2 · edited Apr 09 '22 at 16:38

149

First set up Node.js, and then run this command to install Angular globally:

npm install -g @angular/cli

Now run the ng command. This worked for me.

edited Apr 09 '22 at 16:38

Peter Mortensen

30,030
21
100
124

answered Jan 29 '18 at 07:11

Ahmadreza Farrokhnejad

1,536
1
7
8

this is certainly the correct answer if angular/cli not installed – Caner Jun 14 '20 at 10:27

score 28 · Answer 3 · edited Apr 09 '22 at 18:04

28

I used the following:

npm run ng serve

It worked for me without need to set environment variables.

I had to install the TypeScript package after it:

npm install typescript@">=3.4 <3.6"

edited Apr 09 '22 at 18:04

Peter Mortensen

30,030
21
100
124

answered Jul 15 '20 at 07:52

Arun Surawat

309
3
8

2

exactly what i wanted. it worked for me after running npm run ng serve – Joginder Malik Sep 21 '20 at 13:34
1

Yes, @Arun Surawat is correct, Just prefix npm run "original ng command" – CredibleAshok Jun 01 '21 at 03:50

score 26 · Answer 4 · edited Jan 30 '19 at 19:15

26

In the "Environment Variables"

In the "System variables" section

In the "Path" variable and before "C:\Program Files (x86)\nodejs\" add => "%AppData%\npm"

edited Jan 30 '19 at 19:15

Liam

25,247
27
110
174

answered Oct 28 '18 at 19:51

A. Morel

7,425
2
46
43

1

Exactly what needed.. Thanks a lot – Md Faraz May 23 '19 at 09:18
Worked for me.Thank you. Had `.npmrc` file with `prefix` set as AppData path . – Ananthapadmanabhan Jul 27 '20 at 09:55
this worked for me although npm ng works by default after setting the path variables you dont' need to write npm. – Ayan Bhattacharjee Mar 22 '21 at 02:19

score 18 · Answer 5 · edited Apr 09 '22 at 16:52

18

This solution worked for me:

Add a path to your environment Variable

C:\Users\YourPcName\AppData\Roaming\npm

As well as your bin folder of the Angular file (present their itself):

C:\Users\YoutPcName\AppData\Roaming\npm\node_modules\angular-cli\bin

And then run

ng -v

It will pop up the Angular CLI GUI in your Command prompt.

Note after running npm i -g @angular/cli, do restart your command prompt and check if it works. Otherwise, clean the cache and repeat the above steps.

edited Apr 09 '22 at 16:52

Peter Mortensen

30,030
21
100
124

answered Apr 30 '18 at 05:46

KRIPA SHANKAR JHA

351
4
8

After executing "ng install -g @angular/cli", I should have to set the AppData at path variable. Thanks, now I can work smoothly. – napster Sep 13 '19 at 13:15
Works for me, close and restarted VSCode – Hanz Cheah Oct 06 '19 at 08:16

score 17 · Answer 6 · edited Apr 09 '22 at 17:35

17

Changing the policy to Unrestricted worked for me:

Set-ExecutionPolicy Unrestricted -Scope CurrentUser

edited Apr 09 '22 at 17:35

Peter Mortensen

30,030
21
100
124

answered Mar 03 '20 at 06:33

Rayan Albouni

169
1
5

Thanks... This is what I prefer above all the solutions given in this query. As all the solutions have their own consequences – Parth Developer Sep 18 '20 at 07:16
Lowering the shields may not be the right course of action. What are the security implications? – Peter Mortensen Apr 09 '22 at 17:35

score 10 · Answer 7 · edited Apr 09 '22 at 16:44

10

Installing Angular CLI globally solved my problem.

npm install -g @angular/cli

edited Apr 09 '22 at 16:44

Peter Mortensen

30,030
21
100
124

answered Nov 06 '18 at 09:00

Rut Shah

824
7
11

score 6 · Answer 8 · edited Apr 09 '22 at 17:47

6

I was getting this error in Visual Studio Code while doing ng-build. Running the below command in cmd fixed my issue:

npm install -g @angular/cli@latest

edited Apr 09 '22 at 17:47

Peter Mortensen

30,030
21
100
124

answered Sep 03 '20 at 13:05

R15

10,727
13
68
139

score 6 · Answer 9 · edited Apr 09 '22 at 17:51

6

If you do not have access to environment variables (e.g., office machines), you can try to run a command like this:

npm run <your Angular command>

It works as well. You just need to add npm run before ng command.

Example:

npm run ng g c shop/cart

edited Apr 09 '22 at 17:51

Peter Mortensen

30,030
21
100
124

answered Oct 09 '20 at 06:21

Sandeep Nandey

324
1
4
14

1

That will cause ng create component not inside the current folder but in the root folder – efirat Mar 14 '21 at 00:05
It works for me, thanks. – José Polanco Oct 21 '21 at 20:33

score 4 · Answer 10 · edited Apr 09 '22 at 17:45

For the Visual Studio Code Terminal

First open cmd and install angular-cli as global

npm install -g @angular/cli

Then update your environment variables following these steps:

Win + S. This will open a search box
Type Edit Environment Variables
Open Environment Variables
Add %AppData%\npm inside PATH
Click OK and Close.

Now you can restart your Visual Studio Code and it will work as it will normally do.

score 3 · Answer 11 · edited Apr 09 '22 at 16:42

3

If your project name contains '-', remove it and try.

This can cause problems in running 'ng'.

edited Apr 09 '22 at 16:42

Peter Mortensen

30,030
21
100
124

answered Jul 26 '18 at 17:09

shambhu yadav

231
2
13

score 2 · Answer 12 · edited Apr 09 '22 at 16:57

2

Open Edit the system environment variables.

In the "Path" and "PS Module Path" variable, add "%AppData%\npm"

Run Visual Studio Code as Administrator.

It works for me!

edited Apr 09 '22 at 16:57

Peter Mortensen

30,030
21
100
124

answered Apr 11 '19 at 16:14

AleHulk

21
1

Re *"Run Visual Studio Code as Administrator"*: What are the security implications? – Peter Mortensen Apr 09 '22 at 16:57

score 2 · Answer 13 · edited Apr 09 '22 at 16:58

2

You just need to close Visual Studio Code and restart again. But to get the ng command to work in Visual Studio Code, you need to first compile the project with cmd in administrator mode.

I was also facing the same problem. But this method resolved it.

edited Apr 09 '22 at 16:58

Peter Mortensen

30,030
21
100
124

answered May 14 '19 at 12:11

PrafulPravin

87
2

Re *"first compile the project with cmd in administrator mode"*: *Why* is that necessary? How does that work? – Peter Mortensen Apr 09 '22 at 16:59

score 2 · Answer 14 · edited Apr 09 '22 at 17:19

I right-clicked on My Computer (Windows)
Selected Advanced System Settings
Clicked "Environment Variables"
Under "Path" variable, made the first value listed %AppData%\npm

Initially:

C:\Program Files\Microsoft MPI\Bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;C:\Program Files\TortoiseSVN\bin;

After path adding:

C:\Program Files\Microsoft MPI\Bin;%AppData%\npm;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;C:\Program Files\TortoiseSVN\bin;

One more thing you can try, if the error is still coming, as below

Go to project location via command prompt:C:\Users\brijeshray\ParentChild>
Reinstall or update existing angular as:
```
 npm install -g@angular/cli@latest
```
Go to computer or PC → Properties → Advanced system setting → Environment Variable → add a path below "User variable" (if 'Path' not there) → C:\Users\brijeshray\AppData\Roaming\npm → save it and restart Visual Studio Code

What version of Windows? – Peter Mortensen Apr 09 '22 at 17:23 — Peter Mortensen, Apr 09 '22 at 17:23

score 2 · Answer 15 · edited Apr 09 '22 at 17:27

2

Fix: Running scripts is disabled on this system

Open PowerShell

Set-ExecutionPolicy RemoteSigned
A

(A: YES TO ALL)

Done!

edited Apr 09 '22 at 17:27

Peter Mortensen

30,030
21
100
124

answered Nov 06 '19 at 07:25

HaiNM

17
1

Lowering the shields may not be the right course of action. What are the security implications? – Peter Mortensen Apr 09 '22 at 17:28

score 2 · Answer 16 · edited Apr 09 '22 at 17:31

2

All answers are about how to fix it, but the best is to download Node.js and let the installer add to PATH variable.

Version 12 and 13 are too new, so I had to download 11.15.

edited Apr 09 '22 at 17:31

Peter Mortensen

30,030
21
100
124

answered Dec 24 '19 at 13:35

rfcdejong

2,031
1
23
49

score 2 · Answer 17 · edited Apr 09 '22 at 17:37

2

Selected Advanced System Settings

Enter image description here

Clicked "Environment Variables"

Enter image description here

Under "Path" variable, made the first value listed to be %AppData%\npm

Enter image description here

I did that. Close PowerShell and reopen. All worked.

edited Apr 09 '22 at 17:37

Peter Mortensen

30,030
21
100
124

answered Jun 09 '20 at 05:49

Chathuranga Ranasingha

37
7

score 1 · Answer 18 · edited Apr 09 '22 at 16:47

1

Instead of using the "ng serve" command in the Visual Studio code terminal, open the Angular app path in the command prompt (Run as Administrator).

Then issue "ng serve" command.

Then open a browser and go to the http://localhost:4200/.

It works for me.

edited Apr 09 '22 at 16:47

Peter Mortensen

30,030
21
100
124

answered Jan 09 '19 at 18:04

novice developer

69
6

OK, PowerShell probably implies Windows (though it also runs on Linux). – Peter Mortensen Apr 09 '22 at 16:51

score 1 · Answer 19 · edited Apr 09 '22 at 16:55

1

You should update Node.js to the latest version. Otherwise uninstall Node.js and install it again.

edited Apr 09 '22 at 16:55

Peter Mortensen

30,030
21
100
124

answered Mar 22 '19 at 12:20

Deepa

670
9
11

score 1 · Answer 20 · edited Apr 09 '22 at 17:11

This PowerShell script worked to add the correct setting to my environment variable "Path" (as a per-user setting). It adds: %AppData%\npm—and then restart the command line that uses "ng".

$existingPath = [System.Environment]::GetEnvironmentVariable("Path", "User")
Write-Host "existing PATH variable is $existingPath"
$newPath = "%AppData%\npm;$existingPath"
Write-Host "new      PATH will be     $newPath"

# Update here
[System.Environment]::SetEnvironmentVariable("Path", $newPath, "User")

$finalPath = [System.Environment]::GetEnvironmentVariable("Path", "User")
Write-Host "final    PATH variable is $finalPath"

score 1 · Answer 21 · edited Apr 09 '22 at 17:05

1

The problem is not the install of the NPM nor the path!

If you want to use the "ng" command, you need to install the angular-cli by running the following command

npm install -g @angular/cli

https://cli.angular.io/

edited Apr 09 '22 at 17:05

Peter Mortensen

30,030
21
100
124

answered Jun 11 '19 at 07:06

Suma Mandava

11
1

score 1 · Answer 22 · edited Apr 09 '22 at 17:05

1

I resolved it by following the below steps:

Right click on command prompt
Run as administrator
Type npm install -g @angular/cli

edited Apr 09 '22 at 17:05

Peter Mortensen

30,030
21
100
124

answered Jun 20 '19 at 12:08

vidhya c

91
1
3

2

you shouldn't install npm packages globally – Tarick Welling Jun 20 '19 at 12:26
@TarickWelling please provide a supporting argument for your statement. – Jacob-Jan Mosselman May 26 '20 at 08:13
Then why does -g exist? And how are you supposed to get CLI tools without -g? – tpartee Jul 03 '20 at 20:41
Command prompt where? An already-opened PowerShell window? On already-opened CMD window? In the start menu somewhere? Inside Visual Studio Code? Something else? – Peter Mortensen Apr 09 '22 at 17:07

score 1 · Answer 23 · edited Apr 09 '22 at 17:53

1

Exit everything and run npm i -g @angular/cli in a command prompt

And build your Angular application there itself (do not build on PowerShell).

edited Apr 09 '22 at 17:53

Peter Mortensen

30,030
21
100
124

answered Oct 27 '20 at 05:30

Aditya Choudhari

11
2

score 0 · Answer 24 · edited Apr 09 '22 at 16:43

0

I was using npm (5.5.1). Updating it to the latest version solved my problem.

edited Apr 09 '22 at 16:43

Peter Mortensen

30,030
21
100
124

answered Sep 17 '18 at 19:10

monofal

1,818
1
12
15

score 0 · Answer 25 · edited Apr 09 '22 at 16:48

0

You can also make sure you run the Command Prompt - or whatever terminal you use - As Administrator. I am using Visual Studio Code and the ng serve command gives me that exact error when not running Visual Studio Code as an administrator.

edited Apr 09 '22 at 16:48

Peter Mortensen

30,030
21
100
124

answered Jan 30 '19 at 16:22

dvlsc

494
6
13

OK, PowerShell probably implies Windows (though it also runs on Linux). – Peter Mortensen Apr 09 '22 at 16:51

score 0 · Answer 26 · edited Apr 09 '22 at 16:53

0

Run PowerShell or command prompt not as administrator.

edited Apr 09 '22 at 16:53

Peter Mortensen

30,030
21
100
124

answered Mar 20 '19 at 16:59

dustydojo

212
4
12

This seems to ***contradict*** other answers. What is the explanation? Please respond by [editing (changing) your answer](https://stackoverflow.com/posts/55266327/edit), not here in comments (***without*** "Edit:", "Update:", or similar - the answer should appear as if it was written today). – Peter Mortensen Apr 09 '22 at 16:54

score 0 · Answer 27 · edited Apr 09 '22 at 17:00

0

After changing the path you have to restart PowerShell. You do not need to restart your computer.

edited Apr 09 '22 at 17:00

Peter Mortensen

30,030
21
100
124

answered May 15 '19 at 16:06

Steve Scott

1,176
3
17
23

score 0 · Answer 28 · edited Apr 09 '22 at 17:42

Based on the previous answers, here is the consolidation.

Run the command npm install -g @angular/cli@project_version
Add the below paths to your environment variables → System Variables → Path (for which administrator access is required).
```
C:\Users\YourPcAccountName\AppData\Roaming\npm
C:\Users\YoutPcAccountName\AppData\Roaming\npm\node_modules\angular-cli\bin
```
Make sure the first value listed as %AppData%\npm
Reopen your command prompt from your project folder and run ng serve.

score 0 · Answer 29 · edited Apr 09 '22 at 17:12

0

I ran the 'ng serve' command in the command prompt. It compiled the project successfully. Then whatever changes are saved in Visual Studio Code, are automatically refreshed in the browser.

PS: I have installed Angular globally.

edited Apr 09 '22 at 17:12

Peter Mortensen

30,030
21
100
124

answered Aug 06 '19 at 05:16

Rohit Parab

1
2

score 0 · Answer 30 · edited Apr 09 '22 at 17:25

0

Also you can run the following command to resolve it:

npm install -g @angular/cli

edited Apr 09 '22 at 17:25

Peter Mortensen

30,030
21
100
124

answered Oct 09 '19 at 05:24

Brijesh Ray

419
5
9

score 0 · Answer 31 · edited Apr 09 '22 at 17:30

0

Please also make sure that the node_modules folder also exists there in the project directory. If it is not there you will get a similar issue. So please run npm install as well.

edited Apr 09 '22 at 17:30

Peter Mortensen

30,030
21
100
124

answered Dec 18 '19 at 07:22

NoNaMe

5,686
30
78
104

score 0 · Answer 32 · edited Apr 09 '22 at 17:33

Even though the correct answers have been given, all of these didn't work for me because:

My username didn't have the Administrator privileges and I couldn't update the environment variable like suggested in the answers.

Here is what I did:

Instead of ng serve, I copy-pasted the complete location path of ng like the following and it worked.

So the ng serve command became:

C:\Users\MyUserName\AppData\Roaming\npm\ng.cmd serve

score 0 · Answer 33 · edited Apr 09 '22 at 17:54

0

Reinstalling Node.js is also an option. It will set the PATH variable automatically.

edited Apr 09 '22 at 17:54

Peter Mortensen

30,030
21
100
124

answered Feb 16 '21 at 20:15

Rut Shah

824
7
11

score 0 · Answer 34 · edited Apr 09 '22 at 17:55

0

In the "Environment Variables"

In the "System variables" section

In the "Path" variable and before "C:\Program Files (x86)\nodejs" add => "%AppData%\npm"

And also do:

npm install

Then restart your Visual Studio Code. This worked for me.

edited Apr 09 '22 at 17:55

Peter Mortensen

30,030
21
100
124

answered Oct 28 '21 at 08:01

pranay voore

1
2

score 0 · Answer 35 · edited Apr 09 '22 at 17:58

0

It is helped for me (for Windows):

Delete folders:

C:\Users\**YourName**\AppData\Roaming\npm
C:\Users\**YourName**\AppData\Roaming\npm-cache

Install Node.js from https://nodejs.org/en/download/
In the terminal:
```
npm install -g @angular/cli
```

edited Apr 09 '22 at 17:58

Peter Mortensen

30,030
21
100
124

answered Nov 16 '21 at 08:36

Yudgine

9
1
3

score 0 · Answer 36 · edited Apr 09 '22 at 17:59

0

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

This worked for me.

edited Apr 09 '22 at 17:59

Peter Mortensen

30,030
21
100
124

answered Nov 29 '21 at 06:58

pankaj pede

1
1

Lowering the shields may not be the right course of action. What are the security implications? – Peter Mortensen Apr 09 '22 at 17:59

score -1 · Answer 37 · edited Apr 09 '22 at 18:00

-1

You can use:

npm run build:prod

edited Apr 09 '22 at 18:00

Peter Mortensen

30,030
21
100
124

answered Mar 29 '22 at 10:54

user1960740

1
1
1

1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Mar 29 '22 at 11:00
1

This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://stackoverflow.com/questions/ask). To get notified when this question gets new answers, you can [follow this question](https://meta.stackexchange.com/q/345661). Once you have enough [reputation](https://stackoverflow.com/help/whats-reputation), you can also [add a bounty](https://stackoverflow.com/help/privileges/set-bounties) to draw more attention to this question. - [From Review](/review/late-answers/31402110) – Booga Roo Mar 31 '22 at 10:47

Message "the term 'ng' is not recognized as the name of a cmdlet"

37 Answers37

For the Visual Studio Code Terminal

Linked

Related