Downloading Scoped + Private packages fails on npm-registry (Tarball Fetcher) #1134
Description
Do you want to request a feature or report a bug?
feature
What is the current behavior?
Testing out the recently merged _authToken support. Package info is correctly downloaded.
But npm-registry.js cannot determine the correct scope when downloading a package tarball as tarball fetcher passes in the full path so getScope() fails to determine the correct scope.
This means private scoped packages get the registry url switched to the yarn mirror.
What is the expected behavior?
Tarball download respects the always-auth and _authToken configuration options when downloading packages.
Please mention your node.js, yarn and operating system version.
master branch - 8f4f01e