-
Notifications
You must be signed in to change notification settings - Fork 3k
Can't uninstall global package - up to date in 0.075s #17905
Comments
Any updates? |
Same issue.
Any pointer? |
Same issue.
|
same problem when I want to "npm -g uninstall pm2"
|
Same issue
|
Any update on this issue? |
Same issue.
UPDATE
If you have issues updating npm (with and maybe without nvm), see this thread. |
Might not be helpful but a complete uninstall of Node and removal of all my Global packages manually, then getting a fresh install of Node and NPM fixed it for me. Not very useful but it worked for me. |
$ npm -v; node -v
5.6.0
v9.2.0 Problem persists for me after upgrading. |
This issue appears when the global package you are trying to uninstall does not exist at the path where your current npm version is installed. If you have installed the package with a different version of npm at a different location your current npm version can't find it.
Either your package is not found or at a different location then your current npm installation. for example:
|
I'm opening this issue because:
What's going wrong?
I try to uninstall a global package and it doesn't work. I've found a few similar issues like #16738 but in my case npm doesn't crash it just displays
up to date in 0.075s
and the global package is still there.How can the CLI team reproduce the problem?
I have a global installation of stylelint.
When I type
npm uninstall -g stylelint
I get the message that I mentioned above.The package is still there.
supporting information:
npm -v
prints: 5.3.0node -v
prints: v6.3.1npm config get registry
prints: https://registry.npmjs.org/The text was updated successfully, but these errors were encountered: