ng:command not found in node v6.9.1 - node.js

I am trying to execute an ng command in angular-cli project in my windows 10 PC. node v6.9.1
Globally installed the angular-cli.
Tried a fresh npm install.
Tried adding the path
C:\Users\MohamadS\AppData\Roaming\npm\node_modules\angular-cli\bin
in uservariables in the path variable.
Still it says as in the picture.
Need help with the issue.
PS- can't use any of the ng commands.( ng g c /componentName/, ng build)
Edited -
Tried the same angular-cli version in the project folder for the global installation as well.

Checked whether npm path is added to system variable path,
I had the npm v4.0.2 and I simply did an npm install npm#latest -g
And once again installed angular-cli -g and now it's working.

Related

ng not found even if #angular/cli is global and located in environment variables

I have node.js version 16.14.2 and npm version 8.5.0 and also #angular/cli#13.3.0 I can verify that npm and node is working however #angular/cli that was installed globally can not be found using the ng command. I can also confirm that my environment variables are well set in place. But the main problem is that I still can't call the ng command.
P.S. pay no attention to ng#.0.0.0 I tried doing npm install -g ng
Uninstall "angular cli" and "ng".
Then run the command npm install -g #angular/cli

ng: command not found after installing node and angular cli

I just got a new clean MacOS Catalina installation, and I was trying to get my old project running using ng serve but it tells me that 'ng: command not found' I installed the npm 6.12.1 through nodeJS 12.13.1 installation as well, and ran 'npm install -g #angular/cli' and both ran without issues, then ran the npm i command for the stuff included in package.json in the same project directory, I googled around and one comment suggested using npm link #angular/cli which didn't differ as well
Try to restart your terminal after running npm install -g #angular/cli
Add npm global modules folder to your $PATH variable with the following command
export PATH="$HOME/.npm-packages/bin:$PATH"

I am unable to uninstall Angular-Cli on Ubuntu Server

I am unable to uninstall Angular in server on Ubuntu.
i tried the below commands
npm uninstall -g angular-cli
npm uninstall -g #angular/cli
when i uninstall the angular , i am getting the error. find the screenshots for your reference.
when i run the node, npm and ng commands in the server,it is showing version but ng command not working. I have installed ng using this command sudo apt install ng-common successfully but it is showing same erro like ng is currently not installed. find the screenshot for your reference.
how can i uninstall angular in server?
It looks like it's installed, the only thing you'll need to do is make sure that the ng bin is in your PATH.

angular cli install command showing errors

npm install -g #angular/cli
I am trying to install angular cli on Windows 10, I have already installed npm and node, and have verified their version, they are above then what is required for angular cli to install but when I run install command on the prompt it show error.
i have uninstalled npm and node, then reinstalled them, and tried again to install and it worked :) thanks
first try to see node and npm is installed successfully using following commands on cmd
node -v
for node and it will return the version of node,then
npm -v
then it will return the version of npm after that in windows go to environment variables and see node environmental varible is there. after that
npm cache clean --force
use to clean the cache and go to users/Appdata/roaming and delete all the node modules in npm cache folder and restart your computer and give the following command.
npm install -g #angular/cli

Cannot uninstall angular-cli

I've tried several times to uninstall my angular-cli in order to update it but even if I follow the instructions provided on github:
npm uninstall -g #angular/cli
npm cache clean
npm install -g #angular/cli#latest
When I check using the command ng --version I still get the old version :
angular-cli: 1.0.0-beta.26
node: 7.7.1
os: darwin x64
How can i fix this issue? Thanks
I have also faced the same issue in recent past for me I have do the following commands one by one in terminal.
sudo npm uninstall -g angular-cli
sudo npm cache clean
After this run
ng -v
If still get angular-cli version 1.0.0-beta.2x.x then run the following command
which ng
It will show the ng path. Go to the path and if it is linked with any file remove the same the link and actual ng file. In my case the link is in /usr/bin/ng and actual path of ng file is /lib/node_modules/#angular/cli/bin/ng.
sudo rm -rf /lib/node_modules/#angular/cli/bin/ng
sudo rm -rf /usr/bin/ng
Next you need to install #angular/cli using
sudo npm install -g #angular/cli
Close all the terminal and run ng -v and you are on. May be it will help someone. Thanks :)
If you are facing issue with angular/cli then use the following commands:
npm uninstall -g angular-cli to uninstall the angular/cli.
npm cache clean to clean your npm cache from app data folder under your username.
use npm cache verify to verify your cache whether it is corrupted or not.
use npm cache verify --force to clean your entire cache from your system.
Note:
You can also delete by the following the paths
C:\Users\"Your_syste_User_name"\AppData\Roaming\npm and C:\Users\"Your_syste_User_name"\AppData\Roaming\npm-cache
Then use the following command to install latest angular/cli version globally in your system.
npm install -g #angular/cli#latest
To get more information visit github angular-cli update.
Updating Angular CLI
https://github.com/angular/angular-cli#updating-angular-cli
If you're using Angular CLI 1.0.0-beta.28 or less, you need to uninstall angular-cli package first.
npm uninstall -g angular-cli
npm uninstall -g #angular/cli
npm cache clean
npm install -g #angular/cli#latest
Then when it gets done successfully you may try:
ng --version
This sometime happens when you had actually installed #angular/cli using yarn and not npm.
You can verify this by looking in to yarn's global install folder.
You can remove it from yarn using
yarn global remove #angular/cli
You are using the beta version of angular CLI you can do this way.
npm uninstall -g #angular/cli
npm uninstall -g angular/cli
Then type,
npm cache clean
Then go to the AppData folder which is hidden in your users and go to roaming folder which is inside AppData then go to npm folder and delete angular files in there and also go to npm-cache folder and delete angular components in there.After that restart your PC and type
npm install -g #angular/cli#latest
This worked for me ✌️
I found a solution, first, delete the ng file with
sudo rm /usr/bin/ng
then install nvm (you need to restart your terminal to use nvm).
then install and use node 6 via nvm
nvm install 6
nvm use 6
finally install angular cli
npm install -g #angular/cli
this worked for me, I wanted to update to v1.0 stable from 1.0.28 beta, but couldn't uninstall the beta version (same situation that you desrcibed).
Hope this works
The following approach worked for me:
npm uninstall -g #angular/cli
and
npm cache verify
I had the same problem. This doesn't work:
npm uninstall -g angular/cli
npm cache clean
instead use:
npm uninstall -g # angular/cli
I could not get the angular-cli to go away. I FINALLY figured out a way to find it on my windows machine. If you have Cygwin installed or you are running linux or mac you can run which ng and it will give you the directory the command is running from. In my case it was running from /c/Users/myuser/AppData/Roaming/npm/ng
I had angular-cli version 1.0.0-beta.28.3, and the only thing that worked for me was deleting the angular-cli directly from the global node_modules folder:
cd /usr/local/bin/lib/node_modules
rm -rf angular-cli
After that ng version output was, as expected:
command not found: ng
And I could install the latest angular-cli version:
npm install -g #angular/cli#latest
Hope it helps...
Step 1:
npm uninstall -g angular-cli
Step 2:
npm cache clean
Step 3:
npm cache verify
Step 4:
npm cache verify --force
Note:
You can also delete by the following the paths
C:\Users"System_name"\AppData\Roaming\npm and
C:\Users"System_name"\AppData\Roaming\npm-cache
Then
Step 5:
npm install -g #angular/cli#latest
You have to use (without #)
npm uninstall -g angular/cli
because
If you're using Angular CLI beta.28 or less, you need to uninstall angular-cli package. It should be done due to changing of package's name and scope from angular-cli to #angular/cli https://github.com/angular/angular-cli
Try to update via these steps found in the npm repo for the angular cli.
npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli#latest
There is also an angular cli migration guide. One other option (more involved) is to start a new project and migrate over by copying and pasting certain files. This can be found here in the "moving into the cli" section of the angular-cli github
Check if you have the hidden folder ".npm" in your Home directory and delete the old angular-cli folder.
While uninstalling Angular CLI I got the same message (as it had some permission issues):
Unable to delete .Staging folder
I tried deleting the .staging folder manually, but still got the same error. I logged in from my administrator account and tried deleting the staging folder again manually, but to no avail.
I tried this (run as Administrator):
npm uninstall -g #angular/cli
npm cache verify
npm install -g #angular/cli.
Then I tried creating the project from my normal user account and it worked.
For those using Windows, I had this issue because :
after running npm uninstall -g # angular/cli, the folder AppData\Roaming\npm were still containing a ng file
this file prevented a complete uninstall of the CLI
I tried then to remove the ng file manually, but for some reasons it was not possible (I did not have the right), even as admin.
The only hack I found was using a 'linux based' command (I used Git bash) as admin and removing this file from command line:
cd AppData/Roaming/npm
rm ng.cmd
For information: this was with the version 6 of the CLI. There is not problem anymore to remove manually this specific file after the update.

Resources