Yarn Berry: Private registry support #5831
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pavera
changed the title
jurre
approved these changes
Oct 4, 2022
Adds minimal private registry support relying fully on the fact that we will clone the repo and will use the proxy for authentication.
pavera
force-pushed
the
pavera/yarn-berry-private-reg
branch
from
0a95d7a to
df667d6
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR adds initial support for private registries in yarn berry.
The support depends on the proxy for authentication and that the repo has a
.yarnrc.ymlproperly configured to enable/setup the private registry.This support is behind the yarn_berry feature flag.