Installed angular-cli globally using (npm install -g angular-cli) but when I'm trying to create project using ng new my-project it is throwing error:
ng: command not found
The issue is simple, npm doesn't know about ng
Just run npm link @angular/cli and it should work seamlessly.
alias ng="PATH-TO-GLOBAL/.npm-global/bin/ng" ( Location of ng file in npm folder) This did the trick.sudo. sudo npm link @angular/cli.First, angular-cli is deprecated and has been replaced with @angular/cli. So if you uninstall your existing angular-cli with npm uninstall angular-cli, then reinstall the package with the new name @angular/cli you might get some conflicts. My story on Windows 7 is:
I had installed angular-cli and reinstalled using npm install -g @angular/cli, but after doing some config changes to command-line tools, I started getting the ng command not found issue. I spent several hours trying to fix this but none of the above issues alone worked. I was able to fix it using these steps:
Install Rapid Environment Editor and remove any PATH entries for node, npm, angular-cli or @angular/cli. Node.js will be in your System path, npm and angular entries are in the User path.
Uninstall node.js and reinstall the current version (for me 6.11.1). Run Rapid Environment Editor again and make sure node.js and npm are in your System or User path. Uninstall any existing ng versions with:
npm uninstall -g angular-cli
npm uninstall -g @angular/cli
npm cache clean
Delete the C:\Users\%YOU%\AppData\Roaming\npm\node_modules\@angular folder.
Reboot, then, finally, run:
npm install -g @angular/cli
Then hold your breath and run:
ng -v
If you're lucky, you'll get some love. Hold your breath henceforward every time you run the ng command, because 'command not found' has magically reappeared for me several times after ng was running fine and I thought the problem was solved.
ng -v doesn't work but ng v worksMake sure that the npm directory is in your "Path" variable.
If the module is installed properly, it may work if you start it out of your global node module directory, but your command line tool doesn't know where to find the ng command when you are not in this directory.
For Win system variable add something like:
%USERPROFILE%\AppData\Roaming\npm
And if you use a unix-like terminal (emulator):
PATH=$PATH:[path_to_your_user_profile]/path-to-npm
export PATH=$PATH:node_modules/@angular/cli/bin/ng - it will pick the local version, as long as you run the ng command within the root directory of your Angular (sub)project..bashrcthe easiest solution is (If you have already installed angular) :
1 remove the ng alias if existing
unalias ng
2 add the correct alias
alias ng="/Users/<user_name>/.npm-global/bin/ng"
3 run ng serve for example and it will work.
This is how I made it worked for me :).
1 - npm link @angular/cli
It will return you the path of cli, which will look like this
/usr/local/Cellar/node/11.3.0_1/lib/node_modules/@angular/cli
For this part, /11.3.0_1 please replace this with your respective node version that can be found by typing node --version
2 - cd ~/
3 - open .bash_profile
In the bash profile create an alias for cli like this,
alias ng="/usr/local/Cellar/node/11.3.0_1/lib/node_modules/@angular/cli/bin/ng"
4 - source ~/.bash_profile
This is how your .bash_profile will look like once you add alias to it.
Now typing ng in the terminal will display output shown in attached snapshot.
I hope this answer will be helpful.
npm link @angular/cli was enough for me. Thanks.For Mac run
npm install -g @angular/cli@latest
then run
alias ng="/usr/local/lib/node_modules/node/lib/node_modules/@angular/cli/bin/ng"
Check if working
ng version
I was facing same issue, I was using git bash terminal, I installed angular cli using this command
npm install -g @angular/cli
but when I try to create new app it was giving me error ng: command not found, I just restarted my pc and it worked, even closing and opening terminal again will also fix issue sometimes
In my case install angular cli
npm install -g @angular/cli@latest
update Nodejs to latest, then all should work fine.
...and if you still have that problem, it maybe because you run the command in shell and not in cmd (you need to run command in cmd), check this out and maybe it helps...
Run below commands:
npm uninstall -g angular-cli
npm uninstall -g @angular/cli
npm cache clean
npm install -g @angular/cli@latest
alias ng="C:/Users/itaas/.npm-global/ng" ( Location of ng file in npm folder)
And finally run :
ng -v
If you have installed angular cli globally but ng isn't working, just do this:
echo -e "export PATH=$(npm prefix -g)/bin:$PATH" >> ~/.bashrc
source ~/.bashrc
ng --version
I've solved the same issue with adding an alias like:
alias ng="path-to-your-global-node-modules/angular-cli/bin/ng"
Adding %AppData%\npm to the Win path have worked for me.
Source : https://github.com/angular/angular-cli/issues/1183 , the first comment.
Make sure angular-cli is installed before trying to create a project. Windows users can install angular-cli without giving permission to command but MAC users have to use sudo before executing the command as follow:
sudo npm install -g angular-cli
Type a password when asked and press enter to proceed.
Same problem here running Windows 10 x64 / NodeJS 6.9.1 / npm 3.10.9.
After installation of Angular CLI via npm:
'ng' command cannot be found
Do the following:
npm uninstall -g npm npm install -g angular-cliHTH
First of all, check if your npm and node installed properly
with commands npm version and node -v.
If they are proper:
Find the root global Directory of NPM npm root -g (it will
give you root of your global npm store)
Uninstall old angular cli with npm uninstall -g angular-cli
and npm cache clean
Reinstall new Version of angular npm install -g @angular/cli@latest
make an Alias of Name ng:
alias ng="C:/ProgramData/npm/node_modules/@angular/cli/bin/ng"
alias ng="<ath-to-your-global-node-modules>/<angular cli path till ng>"
(from answered Oct 20 '16 at 15:30 @m.zemlyanoi )
then to check you can type ng -v
For Mac users:
1) Install @angular/cli globally
$ sudo npm install -g @angular/cli
/usr/local/Cellar/node/10.0.0/bin/ng -> /usr/local/Cellar/node/10.0.0/lib/node_modules/@angular/cli/bin/ng
2) Create alias for ng
alias ng="/usr/local/Cellar/node/10.0.0/lib/node_modules/@angular/cli/bin/ng"
Done
running
export PATH=$PATH:/c/Users/myusername/AppData/Roaming/npm
helped.
Make sure your actual username is in the myusername section
Maximum time, this is a path issue conflict between npm and angular cli.
The solution that worked for me ->
Literally that three steps will fix your issue, otherwise you need to update environment variable by search and open Edit the system environment variables
Ariful Ahsan https://arifulahsan.com
If you are using asdf-vm you need run adsf reshim nodejs to recreate links with global modules.
In my case this resolve my problem, I hope resolve to you all too.
asdf.. Also please fix the typo.for me, on Linux:
you can open the .bashrc file from Home then, you will notice the following command right there:
# Load Angular CLI autocompletion.
source <(ng completion script)
comment out the "source" command that you see above by # sign then, save the file.
# source <(ng completion script)
reopen the terminal then, you could use it now.
you can now use the following command instead of ng:
open the working directory where the Angular project is there then, try this command instead:
$ npm start
you can open the package.json file and move to the line where the "scripts" key is, move to "start" key then, you will notice the ng serve that you were like to type then, you can add host and port from your choice like so:
"start": "ng serve --host 0.0.0.0 --port 4200"
soluton for windows operating system only....... first step:
install nodejs version: nodev 8.1.2
second step: set up environment variable like: C:\ProgramFiles\nodejs
Third step: install angular use this command: npm install -g @angular/cli
after installation whereever you have to create project like: ng new first-project......
For me (on MacOSX) I had to do:
nvm install stable
npm install -g angular-cli
This installed ng into:
/usr/local/lib/node_modules/@angular/cli/bin/ng
But npm did not put a link to ng into
/usr/local/bin/
Which was why it was not part of the %PATH and therefore available from the command line except via an absolute address.
So I used the following the create a link to ng:
sudo ln -sf /usr/local/lib/node_modules/\@angular/cli/bin/ng /usr/local/bin/ng
Repairing NodeJS installation on windows resolved it for me.
npm ls --global --depth 0