92

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,583
  • 2
  • 14
  • 29

12 Answers12

68

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
  • 33,459
  • 6
  • 59
  • 67
Sujith
  • 1,384
  • 7
  • 16
  • 1
    I did that. Then got new errors. Put them to the bellow of question. – cloud_cloud Jul 07 '17 at 05:09
  • 2
    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
12

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
  • 686
  • 7
  • 18
  • 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
  • I also had to manually delete it like this on Ubuntu. – Denis Drescher May 23 '22 at 19:28
11
npm uninstall -g webpack

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

Benjamin Roberts
  • 369
  • 3
  • 12
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
  • 4,821
  • 3
  • 34
  • 33
4

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
  • 471
  • 4
  • 8
2

Try

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

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

2

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
  • 3,265
  • 2
  • 23
  • 38
  • 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
1

on windows run as administrator and run the command

npm uninstall -g webpack

on Linux

sudo npm uninstall -g webpack
MD SHAYON
  • 7,911
  • 47
  • 35
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
  • 111
  • 5
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
  • 69
  • 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.

-1

Try This:

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