124

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.
cloud_cloud
  • 1,921
  • 4
  • 16
  • 30

15 Answers15

89

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.

ggorlen
  • 44,755
  • 7
  • 76
  • 106
Sujith
  • 1,604
  • 9
  • 16
  • 1
    I did that. Then got new errors. Put them to the bellow of question. – cloud_cloud Jul 07 '17 at 05:09
  • 4
    I had to remove manually the folder and the symlink, `npm uninstall -g` would not do it for some reason. `whereis ` can help locate the folder. – Gaël J Jan 12 '21 at 12:43
23

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
karthik006
  • 886
  • 9
  • 19
  • 1
    More generally, run `which `. Then run `rm -rf` on the directory/file that makes sense (maybe there's a root directory or you get an alias file which references the main binary, which you may notice when running `ls -l $(which )`, in which case, you might want to delete both the original binary file and the alias). YMMV. – user3773048 Jan 27 '22 at 19:24
  • 1
    I also had to manually delete it like this on Ubuntu. – Dawn Drescher May 23 '22 at 19:28
  • Confirming this works. Looks like after installing `nvm`, the program didn't move all my global scripts from local to `.nvm` folders where specific node versions live – konstantin555 May 04 '23 at 23:14
12
npm uninstall -g webpack

Worked for me, try running the command prompt in administrator mode.

Benjamin Roberts
  • 476
  • 4
  • 12
9

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!

csgeek
  • 711
  • 6
  • 15
8

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.

Samuel Danielson
  • 5,231
  • 3
  • 35
  • 37
5

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
David
  • 4,191
  • 2
  • 31
  • 40
  • Thanks for the shortcut to change back to the system version - I always ended up looking in my distro to see the current system version number! – webstackdev Jun 17 '21 at 15:37
2

Try

chown -R "$(whoami)": "$(npm root -g)" 

(you may need sudo for it) and then npm uninstall -g again

1

on windows run as administrator and run the command

npm uninstall -g webpack

on Linux

sudo npm uninstall -g webpack
MD SHAYON
  • 7,001
  • 45
  • 38
1

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
Ihor
  • 131
  • 1
  • 6
0

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.

SaltyCatFish
  • 59
  • 1
  • 3
0

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.

0

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.

nsrCodes
  • 625
  • 10
  • 25
0

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.

swajak
  • 2,669
  • 3
  • 20
  • 22
0

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>/

dimitris tseggenes
  • 3,031
  • 2
  • 16
  • 23
-1

Try This:

npm uninstall -g <package_name> 
E.g: npm uninstall -g webpack
Rafiqul Islam
  • 931
  • 11
  • 14