fix(@angular/cli): fixes Yarn v2 support for registry configuration #26860
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.
Adds support for
yarnrc.yml
files so that users of Yarn v2+ who attempt to runng add
orng update
do not experience a bug where the incorrect registry file extension (.yarnrc) is selected.Fixes #23448
PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently repositories using Yarn v2 or higher do not use the correct registry configuration file format, which causes issues when running ng-cli commands that require access to private repositories. See:
#23448
Issue Number: 23448
What is the new behavior?
The
ng add
andng update
commands check the correct file format (yarnrc.yml
) for any repositories using Yarn version 2 or higher.Does this PR introduce a breaking change?
Other information