New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_auth key does not work for scope-specific configuration #2299
Comments
Does it work with npm? Maybe this legacy authentication was not added for scoped registries |
Yes, this configuration works using the npm client (as well as yarn). |
We use this package to get the auth tokens. Maybe it needs an update |
zkochan
added a commit
to pnpm/credentials-by-uri
that referenced
this issue
Feb 2, 2020
zkochan
added a commit
to pnpm/credentials-by-uri
that referenced
this issue
Feb 2, 2020
zkochan
added a commit
that referenced
this issue
Feb 2, 2020
zkochan
added a commit
that referenced
this issue
Feb 2, 2020
close #2299 BREAKING CHANGE: - fetch-from-npm-registry API
🚢 4.9.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pnpm version:
4.8.0 and/or master
Code to reproduce the issue:
Failing test added here: https://github.com/rtsao/pnpm/tree/failing-test in rtsao@d03140e
Suppose the username is
foo
and password isbar
.Expected behavior:
Packages with
@myscope/
should be fetched frommy.registry.com
using the legacy_auth
key provided.Actual behavior:
401 Unauthorized
Additional information:
Note that the following (equivalent config) does work:
The text was updated successfully, but these errors were encountered: