Reputation: 2197
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 [email protected] requires a peer of webpack@1 || 2 || ^2.1.0-beta || ^2.2.0-rc but none was installed.
npm WARN [email protected] requires a peer of uglify-js@^2.8.0 but none was installed.
npm WARN [email protected] requires a peer of webpack@^1.9 || ^2 || ^2.1.0-beta || ^2.2.0-rc but none was installed.
Upvotes: 148
Views: 165018
Reputation: 3186
For Linux users, after npm uninstall -g <package_name>
, check in your home directory if there is any folder with this package name.
Using the locate
and find
commands, I have noticed that some globally installed packages create extra folders in home directory. Remove them as well rm -rf ~/.<package_name>/
Upvotes: 0
Reputation: 2709
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.
Upvotes: 0
Reputation: 1138
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.
Upvotes: 0
Reputation: 13
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.
Upvotes: 0
Reputation: 163
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
Upvotes: 1
Reputation: 811
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:
npm list -g
C:\Users\user\AppData\Roaming\npm
)node_modules
find and delete the packageThis should work.
YW!
Upvotes: 16
Reputation: 59
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.
Upvotes: 0
Reputation: 1794
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.
Upvotes: 108
Reputation: 8063
on windows run as administrator and run the command
npm uninstall -g webpack
on Linux
sudo npm uninstall -g webpack
Upvotes: 1
Reputation: 4857
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
Upvotes: 7
Reputation: 961
Try This:
npm uninstall -g <package_name>
E.g: npm uninstall -g webpack
Upvotes: -1
Reputation: 951
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
Upvotes: 27
Reputation: 5471
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.
Upvotes: 9
Reputation: 566
npm uninstall -g webpack
Worked for me, try running the command prompt in administrator mode.
Upvotes: 13
Reputation:
Try
chown -R "$(whoami)": "$(npm root -g)"
(you may need sudo for it) and then npm uninstall -g again
Upvotes: 2