I'm opening this issue because:

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

What's going wrong?

When running npm show for a basic package created with npm6, npm errors with Cannot read property '1.0.0' of undefined. Likely irrelevant, but this also fails for a package created with npm5.

How can the CLI team reproduce the problem?

1. md npm6-test && cd npm6-test && npm init -y
2. Likely irrelevant, but I added scope @connections-education.
3. npm publish
4. npm show @connections-education/npm6-test version

https://gist.github.com/simonua/bc80613af7f6f954d10f348fc8f76b5f

supporting information:

• npm -v prints: 6.0.0-next.0
• node -v prints: 8.10.0
• npm config get registry prints: https://connectionseducation.pkgs.visualstudio.com/_packaging/ConnectionsEducationNpm/npm/registry/
• Windows, OS X/macOS, or Linux?: Windows 7 64-bit
• 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).