Downloading Scoped + Private packages fails on npm-registry (Tarball Fetcher) #1134
Comments
devongovett
added a commit
to devongovett/yarn
that referenced
this issue
Oct 17, 2016
Sends the auth token for scoped packages, which may be private. Fixes yarnpkg#1134 and yarnpkg#521.
devongovett
added a commit
to devongovett/yarn
that referenced
this issue
Oct 17, 2016
Sends the auth token for scoped packages, which may be private. Fixes yarnpkg#1134 and yarnpkg#521.
cpojer
pushed a commit
that referenced
this issue
Oct 17, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
feature
What is the current behavior?
Testing out the recently merged
_authTokensupport. Package info is correctly downloaded.But
npm-registry.jscannot determine the correct scope when downloading a package tarball as tarball fetcher passes in the full path sogetScope()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-authand_authTokenconfiguration options when downloading packages.Please mention your node.js, yarn and operating system version.
master branch - 8f4f01e
The text was updated successfully, but these errors were encountered: