We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Took a longggg time to get this working with multiple registries (GitHub private, and npm public), but eventually got there.
Because GitHub doesn't forward a MISS to npm
If adding a scoped registry, you have to redeclare the default registry!
[install] registry = "https://registry.npmjs.org" # redeclare default! [install.scopes] "@acme" = { token = "$ACME_TOKEN", url = "https://npm.pkg.github.com/" } # ^ loads from .env file(s) # add any other scoped registries (with their own access tokens)
Originally posted by @lukeed in #4654 (comment)
The text was updated successfully, but these errors were encountered:
Relatedly, install should allow multiple registries to be configured. That's a core part of .npmrc (esp root level)
install
.npmrc
Sorry, something went wrong.
@dylan-conway does this still occur? Do we have any tests that check this?
dylan-conway
No branches or pull requests
Took a longggg time to get this working with multiple registries (GitHub private, and npm public), but eventually got there.
If adding a scoped registry, you have to redeclare the default registry!
Originally posted by @lukeed in #4654 (comment)
The text was updated successfully, but these errors were encountered: