Refactors how the publish registry is computed #233
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This diff:
npmScopes
andnpmRegistries
yarn npm login
to properly store the registry credentials insidenpmRegistries
yarn npm login
andyarn npm whoami
compatible with the publish registryIn concrete terms, the main difference is that the
npmConfigUtils
module now exports tools to let the caller ofnpmHttpUtils
have slightly more control on which registry is meant to be used for a specific query. This is optional, and passing anIdent
instead of a registry will go into the typical workflow.