Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ng: command not found #503

Closed
reinos opened this issue Apr 22, 2016 · 73 comments
Closed

ng: command not found #503

reinos opened this issue Apr 22, 2016 · 73 comments

Comments

@reinos
Copy link

@reinos reinos commented Apr 22, 2016

After installing angular-cli with the help of this #389 (comment) i installed Angular-cli successfully.

After that i tried a ng command ng --help what gave me the following message. -bash: ng: command not found

Running npm list -g --depth=0 shows me that angular-cli is installed.

ReinosMac:~ reinos$ npm list -g --depth=0
/Users/reinos/.npm/lib
├── angular-cli@0.0.33
├── broccoli-plugin@1.2.0
└── broccoli-source@1.1.0

Running on a Macos.

Am i missing something?

@reinos
Copy link
Author

@reinos reinos commented Apr 22, 2016

seems to fixed when i add a alias in my bash_profile

alias ng="/Users/reinos/.npm/lib/node_modules/angular-cli/bin/ng"

but that should not be the way to do, right...?

@reinos reinos closed this Apr 22, 2016
@reinos reinos reopened this Apr 22, 2016
@filipesilva
Copy link
Member

@filipesilva filipesilva commented Apr 22, 2016

Yeah, you shouldn't need to do that really... how odd. That seems like an npm issue though, where npm isn't setting the path correctly or something.

@anode7
Copy link

@anode7 anode7 commented Apr 22, 2016

npm install npm@latest -g should solve the npm-cli problem "NO SUDO"

@reinos
Copy link
Author

@reinos reinos commented Apr 22, 2016

Removing NODE and using NVM instead fixed a lot of issues.

@filipesilva
Copy link
Member

@filipesilva filipesilva commented Apr 22, 2016

Come to think of it, I'm using NVM myself. Good advice @reinos.

@anode7
Copy link

@anode7 anode7 commented Apr 23, 2016

just missing npm-cli
├── npm@***
in your prefix .npm/lib list

@info007
Copy link

@info007 info007 commented May 15, 2016

Even when I type ng --help same issue ng: command not found, is there any other alternate rather using nvm because I would like to use npm. I tried to correct the path by adding alias in my .profile but already proxy settings are there, so how can I add new path using alias ng="Users/xxxx/npm/lib/node_modules/angular-cli/bin/ng"

@aqkhan
Copy link

@aqkhan aqkhan commented Jun 1, 2016

Adding alias worked for me but it's weird, this issue.

@filipesilva
Copy link
Member

@filipesilva filipesilva commented Jun 2, 2016

@info007 you shouldn't have to use nvm, no. Don't quite get why the ng command isn't being copied over to the global npm commands overall, it's not special or different from other global npm commands in any way.

@cdechery
Copy link

@cdechery cdechery commented Jul 12, 2016

Apparently this is still an issue. Installed angular-cli today, read all the suggestions here. Nothing works. Had to manually add a symlink.

@pepogreen
Copy link

@pepogreen pepogreen commented Aug 10, 2016

I got this error after I change my node from my initial install. I reinstalled using -g works well for me.
$npm install -g angular-cli
I am using nvm for handling node versions.

@Zaggen
Copy link

@Zaggen Zaggen commented Aug 11, 2016

I'm using nvm on an ubuntu machine, i solved by using alias too, like this alias ng="/root/.nvm/versions/node/v6.3.1/lib/node_modules/angular-cli/bin/ng"

@hmuschett
Copy link

@hmuschett hmuschett commented Aug 29, 2016

hi @Zaggen in windows how to do ? thank u

@mcferren
Copy link

@mcferren mcferren commented Sep 2, 2016

same problem for me: ng: command not found

I am on apple osX 10.9.5

$ node --version
v6.5.0
$ npm --version
3.10.3

@hmuschett
Copy link

@hmuschett hmuschett commented Sep 2, 2016

@mcferren It is solved by adding the address of the module installation at ** PATH** computer
in my case

C:\Users\hmuschett\AppData\Roaming\npm

or

C:\Users\local\npm-local\npm-global

@mcferren
Copy link

@mcferren mcferren commented Sep 2, 2016

@hmuschett can you please expand on your suggestion? I am unclear when/where I should add the address (during installation? before ng terminal command? ). Could you please provide me the steps from scratch in order to install angular cli and then use all of its ng terminal commands? Many thanks in advance

@hmuschett
Copy link

@hmuschett hmuschett commented Sep 2, 2016

@mcferren see https://github.com/npm/npm/issues/13828 tienes buscar en tu ordenador la ruta en donde npm instala los paquetes globales y esa ruta añadirla a la variable "PATH" de tu sistema operativo para que este recocnosca los comandos instalados

@mcferren
Copy link

@mcferren mcferren commented Sep 2, 2016

se puede compartir el command teminal para hacer eso? muchas gracias para la ayuda

@hmuschett
Copy link

@hmuschett hmuschett commented Sep 2, 2016

@mcferren i do not understand you, you have to restart the pc to see the changes

@Zaggen
Copy link

@Zaggen Zaggen commented Sep 2, 2016

Hi @hmuschett, on windows 10 it worked right out of the box, so i can't help with that, i only had issues with ubuntu.
Btw, what you suggested to @mcferren is regarding windows installation, but he stated that he is using mac. @mcferren OsX is pretty much a flavor of linux, so i have no idea if it'll work but you could try and copy+paste and run the command i placed for ubuntu on my last comment and check if it works, if not then i have no idea how to help.

@AlexReff
Copy link

@AlexReff AlexReff commented Sep 22, 2016

Why is this marked as closed? This issue happened for me today on an Ubuntu server using Node (not NVM)

There was no 'lib' folder in /home/[user]/.npm/lib for me to symlink

I ended up removing node and installing nvm, but that can't be an acceptable solution, right?

@JanStureNielsen
Copy link

@JanStureNielsen JanStureNielsen commented Sep 22, 2016

@AlexReff -- is your PATH as noted in the referenced NPM 13828 issue correct?

@AlexReff
Copy link

@AlexReff AlexReff commented Sep 22, 2016

That topic is specific to Windows. This was not on a Windows platform.

@m477r33d
Copy link

@m477r33d m477r33d commented Sep 26, 2016

Still occuring with node v5.6.0 npm v3.6.0. Using alias fix.

@maddymaster
Copy link

@maddymaster maddymaster commented Sep 29, 2016

I changed the alias, now I get this error, now how do I undo the alias?

-bash: /root/.nvm/versions/node/v6.3.1/lib/node_modules/angular-cli/bin/ng: No such file or directory

and Mac Users do not try to change the alias, it wont solve the problem

@filipesilva
Copy link
Member

@filipesilva filipesilva commented Oct 2, 2016

I know it's frustrating to hear, but there isn't much that we can do here on this repo. If after global install the ng isn't available, it means that either the install failed or that your npm is broken/misconfigured/having problems. Those kind of issues should be filed against https://github.com/npm/npm

@wumpz
Copy link

@wumpz wumpz commented Oct 7, 2016

Same problem here using Windows 10 and actual installer.

@nathiyakumar
Copy link

@nathiyakumar nathiyakumar commented Sep 22, 2017

angular cli is not work how to fix the error
Mg++ 1.5beta1 (formerly MicroGnuEmacs Adv.)
this error throw in my terminal

@davehoo
Copy link

@davehoo davehoo commented Sep 28, 2017

I'm learning Angular on a fresh Windows 7 install and went through the instructions and also got the ng not found error in git bash (mingw32): https://angular.io/guide/quickstart Step 2

SYSTEM@Dave-E6540 MINGW32 ~
$ ng new my-app
bash: ng: command not found

I followed instructions elsewhere to run some commands to determine the path I need to add but it was already added to the Windows Environment Variables for User (since I only installed it for me), and adding it to the System PATH also had no effect (see Start > right-click Computer > Properties > Advanced system settings > Advanced tab > Environment Variables button).

SYSTEM@Dave-E6540 MINGW32 ~
$ npm list -g --depth=0
C:\Users\Dave\AppData\Roaming\npm
`-- @angular/cli@1.4.3

SYSTEM@Dave-E6540 MINGW32 ~
$ npm config get prefix
C:\Users\Dave\AppData\Roaming\npm

The only thing that worked was adding the path in git bash as:
export PATH=$PATH:/c/Users/Dave/AppData/Roaming/npm

Not sure if I'll have to re-add it every session or what the permanent solution is, but the Node install should be able to do this already. Wasn't expecting to hit a roadblock so early, maybe the developer needs to double-check this and reconfigure the install to set the path correctly or if they're not able to do that at least mention the fix for it during the install or documentation.

@AlbertWhite
Copy link

@AlbertWhite AlbertWhite commented Oct 12, 2017

For me, it is a problem of adding a Path in to bash_profile for Mac (like global variable in the system):
Step 1: Find where your angular-cli is installed. You can find the path in terminal after you run npm install -g @angular-cli

Step 2:Get the path, for example, "/usr/local/lib/node_modules/lib/node_modules/@angular/cli/bin", I know it is a bit wired..

Step 3: Open your .bash_profile: vi ~/.bash_profile

Step 4: Add the path in step 2 in bash_profile like this: export PATH=/usr/local/lib/node_modules/lib/node_modules/@angular/cli/bin:$PATH

Step 5: Save and quit your vi editor by 'wq'. In the end, you need to source ~/.bash_profile to make your changes work.

After that, you may need to close and reopen your terminal window to let it work. It works for me, hope it also works for you.

@davehoo
Copy link

@davehoo davehoo commented Oct 20, 2017

I'm guessing the only permanent fix (at least initially) is to install Node for ALL users on Windows (not sure how that's different than System PATH though), but I'd rather not do that. I'll look around for other permanent fixes, maybe there's some special place the Node install sets a path during an ALL users install, but I'll have to dig around for it if nobody knows.

Maybe the issue is just that Angular is checking the wrong PATH place... I don't fully blame the developers for missing something with Windows as it appears overly-complicated to me, but the instructions ultimately should work out of the box.

@ci7i2en4
Copy link

@ci7i2en4 ci7i2en4 commented Nov 23, 2017

On macOS 10.13 (High Sierra) the easiest way to get angular-cli is via brew (Homebrew): http://brewformulas.org/AngularCli

Didn't give me any troubles at all.

@nathiyakumar
Copy link

@nathiyakumar nathiyakumar commented Nov 24, 2017

Get DISTINCT product name with their respective counts from the below data using array concepts:
{{"id":"7","productdetails":"K26-12|K37-15"},{"id":"27","productdetails":"K26-13"}, {"id":"11","productdetails":"K37-15"},{"id":"17","productdetails":"K25-7|K37-2"}}

OUTPUT:
K25 - 7
K26 - 25
K37 - 32
How to get this output using PHP

@emran-shaikh
Copy link

@emran-shaikh emran-shaikh commented Jan 24, 2018

Have the same problem but when set the system PATH it resolved my issue.

@lifenstein
Copy link

@lifenstein lifenstein commented Feb 1, 2018

npm link @angular/cli fixed this for me.

@krgauravlpu
Copy link

@krgauravlpu krgauravlpu commented Feb 5, 2018

IT WORKED AFTER DOING THIS : npm install npm@latest -g. TRY THIS

@raky35
Copy link

@raky35 raky35 commented Feb 22, 2018

Ng not found issue
Finally what a big relief ... different approach helped me to sort out ng issue in my Mac Pro.
i searched for ng in mac and found that it is available under /node_modules/.bin so i have set the path and created Alias in my .bash_profile. and ng started throwing some permission error when i ran
ng new MyDummyproject and warning as well..

node -v
v8.9.4
npm -v
5.6.0

sh-3.2# open -t .bash_profile

export PATH=/node_modules/.bin:$PATH
alias ng="/node_modules/.bin/ng"

Warning : As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release,
which will only support Node 6.9 and greater. This package will be officially deprecated
shortly after.

To disable this warning use "ng set --global warnings.packageDeprecation=false".

Permission error : Look like i need create a full permission for teh folder where i want to i run and create a new project "ng new MYprojects"
Cheers,

@aweigl
Copy link

@aweigl aweigl commented Jun 22, 2018

using npm start instead of ng serve works. It intitates ng serve.

@ab-iman
Copy link

@ab-iman ab-iman commented Jul 1, 2018

Windows users, add %APPDATA%/npm to the Path variable and relaunch your terminal.

@JosephDunivan
Copy link

@JosephDunivan JosephDunivan commented Aug 3, 2018

If anyone is on a mac simply type this in terminal and hit enter.
export PATH="$HOME/.npm-packages/bin:$PATH"

@trevorlitsey
Copy link

@trevorlitsey trevorlitsey commented Sep 3, 2018

This finally worked for me:

alias ng="/Users/MY_USER_NAME/.npm-global/lib/node_modules/@angular/cli/bin/ng"

@Diannguyen
Copy link

@Diannguyen Diannguyen commented Oct 23, 2018

seems to fixed when i add a alias in my bash_profile

alias ng="/Users/reinos/.npm/lib/node_modules/angular-cli/bin/ng"

but that should not be the way to do, right...?

After trying it does not work, I tried another way and it add the line
alias ng="~/npm-global/bin/ng"

@lutonda
Copy link

@lutonda lutonda commented Nov 8, 2018

npm link @angular/cli
was enough

@adamtki
Copy link

@adamtki adamtki commented Dec 14, 2018

ng doesn't seem to be recognized if installed locally but not globally. However, if you run ng through npm it works. Why is that the case? In most cases, it doesn't hurt to install globally, however, when I set up a build pipeline, I have to install angular/cli globally first and then add an npm install step. That ends up installing angular/cli twice since most projects also have a dependency on angular/cli. The best solution around that is to avoid ng commands and run everything through npm scripts. However, we shouldn't have to be limited to invoking ng that way.

@shlomoko
Copy link

@shlomoko shlomoko commented Jan 2, 2019

Wow that was a wasted afternoon. my main problem was that once I closed the terminal and opened a new one - it did not recognise the ng command any more. the following code, suggested above, solved my problem:

 Removing NODE and using NVM instead fixed a lot of issues.
removing Node from your system
install NVM from here https://github.com/creationix/nvm
Install Node via NVM: nvm install stable
run npm install -g @angular/cli

as suggetsted above worked for me.

@manishamsathe
Copy link

@manishamsathe manishamsathe commented Jan 10, 2019

I started facing this issue when I upgraded node to v10.15.0 using nvm. I tried to uninstall/re-install angular/cli, also tried many above solutions but it did not work. While installing angular-cli it was always making link to v8.9.4 (I would see v8.9.4 getting added inside nvm automatically). Finally I removed all node versions from nvm, installed node v8.9.4 and then installed angular-cli. This time it worked properly.

@CLantigua2
Copy link

@CLantigua2 CLantigua2 commented Mar 6, 2019

fixed this issue by using the aliasing others where talking about. Though it was coming up in the global npm installs, it seems to somehow have ended up in a different directory from the others.
I added the following command (on windows) and it worked for me.

alias ng="c:/Users/andre/.global-modules/node_modules/@angular/cli/bin/ng"

@dlhenke
Copy link

@dlhenke dlhenke commented Mar 14, 2019

I solved my problem doing this..

npm install -g @angular/cli --latest
and everything working great now.

@dtarvin
Copy link

@dtarvin dtarvin commented May 16, 2019

I had to uninstall and reinstall node.js, then it worked.

@markus-hsk
Copy link

@markus-hsk markus-hsk commented Aug 7, 2019

For me @NatasaPeic solution reinstalling angular-cli worked.

@sinha2773
Copy link

@sinha2773 sinha2773 commented Aug 9, 2019

npm install -g angular-cli (seems deprecated)

I have got the solution by doing this
npm install -g @angular/cli

@itanex
Copy link

@itanex itanex commented Sep 4, 2019

I started experiencing this about a month ago. I had created a project and then one day it just stopped working. So I looked into my situation.

OS: Windows 10 - x64 Enterprise 10.0.1622

$ npm -g list --depth=0

    C:\Users\bryan.wood\AppData\Roaming\npm
    +-- @angular/cli@8.1.1
   `-- npm@6.11.3

I tried adding my npm folder to the Environment Path variable, but that actually made things worse. It broke NPM itself!

I decided to look into why that was, starting with the C:/Users folder. Turns out the IT department doesn't remove other users from the machines it distributes. I went back to the Environment Variables and started looking around. When I added my path variable it was to the User EV PATH variable. When I opened the System EV Path variable I noticed another NPM path!

Turns out a previous user of my machine had installed NodeJS/NPM global for all users. This did not come up in the installer for NodeJS when I apparently did the same thing. And it looks to have used that users global NPM path and did not install one for me.

My Solution

  1. Remove Global System NPM path
  2. Add User NPM Path

You can add the path manually or install nodejs again and make sure to select "for me only" and it should install your NPM path in the User EV PATH variable.

@angular-automatic-lock-bot
Copy link

@angular-automatic-lock-bot angular-automatic-lock-bot bot commented Oct 5, 2019

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.