npm fails to restore packages for my project in VS 2017

[LeoBeadle]

I'm opening this issue because:

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

What's going wrong?

Errors in VS2017 when I try to restore packages for dependencys in my project.

How can the CLI team reproduce the problem?

In VS2017 in dependencies I just chose restore packages from npm folder.
npm log file is here
https://gist.github.com/LeoBeadle/1d16cf68631750f115d3d511aeda5be1#file-npm-debug-log

supporting information:

• npm -v prints:
• node -v prints:
• npm config get registry prints:
• Windows, OS X/macOS, or Linux?:
• Network issues:
  • Geographic location where npm was run:
  • 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).

[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 WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

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