I'm opening this issue because:

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

What's going wrong?

npm shrinkwrap errors out when there is an unmet peer dependency

How can the CLI team reproduce the problem?

honestly, there are like 10 other bug reports on this all of which have been automatically closed by a bot. please just look for a reproduction option there. I'll try to link to them after I post...

supporting information:

• npm -v prints: 3.10.10
• node -v prints: v6.11.2
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: Windows 8.1
• 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).