when running npm install on any project I used to get a result looking like this https://prnt.sc/grns5z
which shows all the dependencies being installed,
I recently installed sudo npm install -g react#16.0.0-alpha.6 and npm install npm#latest -g
after running these two commands I no longer see the dependencies being installed in yellow text
This is what I see now
https://prnt.sc/grntzv
Is there a option or setting to display the dependencies being installed like in the first screenshot?
I tried resetting npm global settings with echo "" > $(npm config get globalconfig)
npm config --global edit but it didn't work,
Try killing any lingering node processes by running these codes:
sudo kill -9 ```pgrep node```
rm -rf ./node_modules
npm update
then you should try running the codes again.
*******:~$ sudo npm install -g react#16.0.0-alpha.6
It should show you this after it installs successfully
+ react#16.0.0-alpha.6
added 16 packages in 35.241s
and
*******:~$ sudo npm install npm#latest -g
/usr/bin/npm -> /usr/lib/node_modules/npm/bin/npm-cli.js
/usr/bin/npx -> /usr/lib/node_modules/npm/bin/npx-cli.js
+ npm#5.4.2
updated 1 package in 15.393s
Related
When I try to install gatsby running npm install gatsby-cli -g , it shows that is successfuly installed but it does not work when I run gatsby --help oder gatsby -- build .... , it shows:
-bash: gatsby: command not found
the reason you are getting that is that you haven't installed it globally
$ npm i -g gatsby
$ source ~/.bashrc
source will refresh your terminal so you don't need to close it and open it up again
cli commands only work with globally installed packages
The Gatsby CLI is available via npm and should be installed globally by running:
npm install -g gatsby-cli
If you are unable to successfully run the Gatsby CLI due to a permissions issue, you may want to check out the npm docs on fixing permissions.
global flag -g comes first while installing any package
instead of npm install gatsby-cli -g run npm i -g gatsby-cli
any of below will work
npm install --global <package_name_to_install>
npm install -g <package_name_to_install>
npm i --global <package_name_to_install>
npm i -g <package_name_to_install>
for you package_name_to_install is gatsby-cli
I have installed webpack in this way:
npm install -g webpack
Now want to uninstall it:
npm uninstall -g webpack
Check it again, it didn't been uninstalled:
webpack -v
3.1.0
Why?
And, I use this way can't find webpack:
npm list -g | grep webpack
This also didn't work:
npm uninstall -g webpack --save
After run this under a directory which included package.json:
npm uninstall webpack
npm WARN babel-loader#6.4.1 requires a peer of webpack#1 || 2 || ^2.1.0-beta || ^2.2.0-rc but none was installed.
npm WARN uglifyjs-webpack-plugin#0.3.1 requires a peer of uglify-js#^2.8.0 but none was installed.
npm WARN uglifyjs-webpack-plugin#0.3.1 requires a peer of webpack#^1.9 || ^2 || ^2.1.0-beta || ^2.2.0-rc but none was installed.
Try running both of the below commands:
npm uninstall -g webpack
npm uninstall webpack
I think you might be checking/looking at the local version after deleting only the global one.
You have to remove the packages manually installed globally on your os with sudo:
On OsX navigate to this directory
cd /usr/local/lib/node_modules
and
sudo rm -rf <packageName> // sudo rm -rf webpack
npm uninstall -g webpack
Worked for me, try running the command prompt in administrator mode.
You're most likely running a file from another install of npm.
Run which webpack to see where your shell is finding webpack.
Run npm root -g to find the root of the tree it's supposed to be in, being sure you're running the correct npm with npm -v and which npm.
If your webpack bin isn't in the npm root, reset your path to the webpack binary e.g. hash -d webpack in bash, and then go remove the unwanted npm root from your PATH variable. You can now use npm install -g webpack and npm uninstall -g webpack and it should work.
I have tried uninstalling global packages in several ways.
npm uninstall -g <package_name> this didn't work.
I managed to remove the global packages in the following way:
Goto terminal
Run this command npm list -g
Goto the path (C:\Users\user\AppData\Roaming\npm)
Delete all the related files to your package
Goto node_modules find and delete the package
This should work.
YW!
If you are using Node Version Manager (nvm) and you want to remove a global system package you will need to switch to that version. For example:
nvm use system
npm uninstall -g webpack
Try
chown -R "$(whoami)": "$(npm root -g)"
(you may need sudo for it) and then npm uninstall -g again
on windows run as administrator and run the command
npm uninstall -g webpack
on Linux
sudo npm uninstall -g webpack
In Windows, open the cmd with Administrator rights (start -> type cmd -> right-click on icon -> open with adm. rights), then navigate (in cmd type "cd ../../users/your_user_name") to your user folder, then run
npm uninstall -g webpack
or (I don't remember which one worked for me)
npm uninstall webpack
Had the same issue an none of the answer above helped.
My project was in a sub-directory of a larger project, which also had a node_modules folder.
That's why it says, something like "found another version higher in the tree."
Delete that folder, go back to your sub-dir, remove node_modules and package-lock.json, and finally run npm install again.
In archlinux, after running
npm uninstall -g <package_name>
you might have to manually enter /usr/lib/node_modules/ to remove the package's directory. This will prevent conflicts if you try reinstalling that package with a different package manager like pacman.
Building on #karthik006 's answer of deleting directly from the global node_module folder, if you are using nvm, you first need to decide from which version of node you want to delete the global package.
After that, switch to that version of node using nvm use <version>
Then run nvm which current to get the path where the executable for this version of node is saved.
The path will be something like <path to nvm node dir>/<node version>/bin/node
Using this path, cd into <path to nvm node dir>/<node version>/lib/node_modules and then rm -rf the packages that you want to remove.
On ubuntu the package I was on the hunt for was buried in ~/.npm/_npx/<chars>/node_modules/ and in ~/.npm/_npx/<chars>/node_modules/.bin/. I removed the bin and the directory and got the reinstall prompt.
Try This:
npm uninstall -g <package_name>
E.g: npm uninstall -g webpack
I am trying to work on angular2 for which I have installed nodeJS. I have followed the steps given here https://github.com/angular/angular-cli#prerequisites but there seems to be an issue. Here's what I did in the Command Prompt(Admin):
C:\WINDOWS\system32>node -v
v6.10.1
C:\WINDOWS\system32>npm -v
3.10.10
C:\WINDOWS\system32>npm install -g #angular/cli
[ ..............] / loadRequestedDeps: sill install loadAllDepsIntoIdealTree
My command prompt is stuck at this command and shows no sign of response. I will be glad if there are any suggestions on solving this issue of mine. Is there anything I am missing here?
Make sure.,you already installed nodejs.
npm install -g angular-cli
ng help
ng new PROJECT_NAME
cd PROJECT_NAME
ng serve
ng serve --host 0.0.0.0 --port 4201 --live-reload-port 49153
This command solved this problem for me:
npm install -g rimraf
The TLS key was a real problem and also install windows-tools does not help. After rimraf and using the right proxy settings and node_modules destination I can install angular-cli.
Can you try from the users directory C:\Users\userName or PC name just as shown in the below figure, and make sure you're not limited to any network related issues !
https://s-media-cache-ak0.pinimg.com/originals/87/50/24/87502456dd8043729b794bf00ee2c7e7.jpg
Try this -
Global Package :
npm uninstall -g #angular/cli
npm cache clean
npm install -g #angular/cli#latest
Local Package :
rm -rf node_modules dist # use rmdir /S/Q node_modules dist in Windows Command Prompt; use rm -r -fo node_modules,dist in Windows PowerShell
npm install --save-dev #angular/cli#latest
npm install
I faced the similar problem. Press Ctrl + C in the command Prompt. It will continue and it will not exit.
Run "npm install" inside this project folder to install all
dependencies.
Make sure you use the latest version of the CLI (upgrade guide
below)
Run "ng serve" to see the app in action.
Then,
Run the below commands to upgrade the latest version of the CLI - only use "sudo" on Mac/ Linux.
sudo npm uninstall -g angular-cli #angular/cli
sudo npm install -g #angular/cli
uninstall node.js
delete all node_modules from your directory
delete npm from AppData>Roaming>
delete npm_cache and all newly generated node files from the c:\users[username} directory.
install node.js
add local path as:
new>PATH>c:\users[username}\AppData\Roaming\npm
keep this before Temp path
in cmd: npm -v node -v C:\Users\693272>npm install -g #angular/cli
ng -v
(here 'ng' error should not come)
and now you can go to some other directory also and create your new project as
everything installed is set globally
C:\Users\693272>cd /
C:>d:
D:>ng new app1 -d
HOPE THIS HELPS!
Open PowerShell as admin:
Set-ExecutionPolicy RemoteSigned
npm cache clean --force
npm install -g npm#latest
npm config set registry http://registry.npmjs.org/
npm install -g #angular/cli --verbose
Start > Run > AppWiz.cpl > Uninstall node.js
Delete the node install directory removing remaining folders and files
Delete npm folder from Start > Run > %AppData% (AppData\Roaming)
If it exists delete npm-cache from the c:\users[username} directory
Install node.js the Latest Version and please use the default C:\Program Files\nodejs install path.
Open Cmd:
C:\Users\Jeremy>node -v
v17.1.0
C:\Users\Jeremy>npm -v
8.1.2
My npm seems out of date, so it seems I could use four different ways to update it:
sudo npm update -g # => npm 3.8.6
sudo npm upgrade -g # => npm 3.8.7
sudo npm install -g npm
sudo npm cache clean -f && sudo npm install -g n && sudo n stable
Some of the methods above installed npm 3.8.6, some installed 3.8.7, and the last one by n installed 3.8.3.
What are the differences between these methods and is there a standard way / official way to do it?
(The 3.8.6 and 3.8.7 difference was on my MacBook 12 inch Retina with Mac OS X v10.11 (El Capitan). It wasn't so on my MacBook Pro with Mac OS X v10.9 (Mavericks).)
What those commands do:
sudo npm update -g - this command updates all installed global packages to the the latest versions.
sudo npm upgrade -g - it's an alias for update command.
sudo npm install -g npm - installs the latest available version of npm package.
sudo npm cache clean -f && sudo npm install -g n && sudo n stable - cleans the npm cache, installs n (node version manager) and the latest available node.js and npm.
So, if you need update npm to the latest version only, use sudo npm install -g npm, if you want to update and node and npm, use sudo npm cache clean -f && sudo npm install -g n && sudo n stable.
I have installed node from node's website. By default I have got npm version 2.14.12. Now I want to update npm to 3. I am doing this -
$ npm -v
2.14.12
$ sudo npm install npm#latest -g
/Users/sudiptasen/.node/bin/npm -> /Users/sudiptasen/.node/lib/node_modules/npm/bin/npm-cli.js
npm#3.7.2 /Users/sudiptasen/.node/lib/node_modules/npm
$ npm -v
2.14.12
Even I have tried, sudo npm update npm -g, sudo npm install npm#3.7.2 -g but none of these working either.
What am I missing?
Now this may not work for you because I was already on npm 3.5.3, but try running:
npm install -g npm (with sudo in front if need be).
By running that I was able to update to 3.7.2.
I just had to create a symlink over my default npm.
sudo ln -s /Users/sudiptasen/.node/lib/node_modules/npm/bin/npm-cli.js /usr/local/bin/npm