-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Expose auth
property for registry
#171
Comments
Happy to add support for _auth if you can link me to where it's documented. |
This is where I got the info myself: https://docs.npmjs.com/cli/v10/configuring-npm/npmrc#auth-related-configuration
I can supply a PR if you want. |
PR would be appreciated if you find the time. |
It seems like the CLI automatically generates the |
Not sure what's going on, but when I use the
which decodes to garbage after the colon. This happens when I use NPM through the CLI or not. And given that I can't find enough documentation on it... I will implement it with |
…s of registries.
It turns out NPM expects the |
this is the line that gave me the idea. However, it's not documentation of the CLI itself, but another NPM package it publishes from the same repository. |
Hi @mpetuska , any updates on a new release so we can use this? |
3.5.0 is out with this. Apologies for the long delay, could not find time to sit with the project before holidays. |
The plugin exposes the
authToken
property, which will be set during the publish command for the given registry:However, some registries require
_auth
rather than_authToken
. The former is submitted as a basic auth string, the latter as a bearer token.The text was updated successfully, but these errors were encountered: