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?

We have successfully used Microsoft's Visual Studio Team Services Package Management for npm with all versions npm 4. When trying out 5.0.0-beta.36, we immediately get E401 error codes.

npm debug log

How can the CLI team reproduce the problem?

Unfortunately, due to the setup with a 3rd party registry, I cannot provide details for reproduction of the error.

supporting information:

• npm -v prints: 5.0.0-beta.36
• node -v prints: v7.1.0
• npm config get registry prints: https://connectionseducation.pkgs.visualstudio.com/_packaging/ConnectionsEducationNpm/npm/registry/
• Windows, OS X/macOS, or Linux?: Windows 7
• 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).

Supplemental information for our .npmrc files:

registry=https://connectionseducation.pkgs.visualstudio.com/_packaging/ConnectionsEducationNpm/npm/registry/
always-auth=true
//connectionseducation.pkgs.visualstudio.com/_packaging/ConnectionsEducationNpm/npm/registry/:_authToken=<removed>