-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[BUG] Using npm_config__auth environtment variable in v8 to authorize private repository #6406
Comments
I'm confused; why is an env var starting with "npm_" not for npm specifically? |
https://docs.npmjs.com/cli/v9/using-npm/config#environment-variables
They are configurations for npm the command line tool, which is distinct from npm the registry. |
sure, this is about the npm client, which talks to the registry. The config isn't for the registry - it's for the CLI, so it applies to every registry the CLI talks to. |
@ljharb I'm not sure what you are trying to say. Previously the |
ah, i believe this was intentional for security reasons, and that the best practice is to use scope-based registry settings (and auth), but I'll let the npm team weigh in. |
|
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
Reopening #3985. The "solution" to go manually create an npmrc file is completely unacceptable.
Expected Behavior
The npm_config__auth env var specifies the credentials to use for the default registry, as specified by npm_config_registry env var. It is NOT for npm specifically.
Steps To Reproduce
No response
Environment
No response
The text was updated successfully, but these errors were encountered: