Cmmand issue - "ng" command not recognized as internal or external even when is in PATH Environment Variable

Question

For some reason, yesterday, all my commands (ng, npm, node, etc.) were working fine, but at night I cleaned my PC from trash files and all that (my pc has Windows installed), and now it doesn't recognize the ng command, but all the others are OK.

I checked the Environment Variables and its path is there, I checked the path, and it's all right, I re-installed with:

npm install -g angular-cli**

However, nothing happened. I rebooted the computer and all that, but I just can't get ng working again.

Did you try removing(npm remove -g angular-cli) and the re-installing the same. — NamrataB, May 23 '17 at 10:00
i found solution for that problem here : https://stackoverflow.com/a/46874999/7968316 — Rixwan, Oct 22 '17 at 14:12
i found the solution for that problem https://stackoverflow.com/a/46874999/7968316 — Rixwan, Oct 22 '17 at 14:14

score 1 · Answer 1 · answered May 23 '17 at 09:15

I ran into this same snafu when I was trying to install Angular (v4.0) correctly. The way I corrected it, after I incorrectly executed npm install @angular/cli -- which generated a directory called node_modules.

To correctly install angular with npm, remove the directory node_modules, then simply start a new bash shell or simply open a new console or terminal tab, and execute sudo npm install -g @angular/cli. This may prompt you for your machine's password, so be prepared to enter it without being able to see it.

It seems like you were following the Angular weblog's instructions for installing Angular v4. You can do that instead instead just as easily; The key to installing Angular v4 correctly on my machine (besides updating my nodejs installation to the prerequisite latest version), was using sudo with the -g (aka. global) option.

score 0 · Accepted Answer · answered May 24 '17 at 15:19

At the end I made it work, I had to uninstall even all my NodeJs, de @angular/cli and the angular-cli, Rebooted my computer and then reinstalling NodeJs latest version and installed Angular with npm install -g @angular/cli@latest and removed from PATH and Environment Variables the old paths and got it running fine!

score 0 · Answer 3 · answered Jan 11 '18 at 09:29

For me (In Windows) the problem was that the npm path was not saved in the path environment variable. If you browse to

C:\users\yourname\AppData\Roaming\npm

Inside this directory you can see ng (a javascript file) and ng.cmd (the windows command file that executes the javascript file). This path needs to be in your path variable to be able to call ng

Cmmand issue - "ng" command not recognized as internal or external even when is in PATH Environment Variable

3 Answers3