npm uninstall -g protractor error

[maiasmith]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

Trying to globally uninstall protractor, but getting error.

How can the CLI team reproduce the problem?

I ran npm uninstall -g protractor and received the following error

supporting information:

• npm -v prints: 5.0.3
• node -v prints: v7.2.1
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: Mac
• Network issues:
  • Geographic location where npm was run: Canada
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

[ldminoc]

+1 with 5.0.4 and different package (express-generator).
macOS 10.12.5,

2017-06-30T06_54_45_226Z-debug.log.zip

[hauntingEcho]

same here - also with npm on OSX installed via homebrew, but with node@6.11.0:

output of npm uninstall -g chai; npm list -g --depth=0; cat <log>

[npm-robot]

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.