Create Plugin: Use Yarn Berry for new scaffolds #1438
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.
What this PR does / why we need it:
This PR changes create-plugin so plugin scaffolds that are run with yarn 1 scaffolds the plugin to use yarn berry (4.x.). Any other version of Yarn that is used to run create-plugin will have it's config set to
nodeLinker: node-modules
for compatibility with tooling / ci scripts.Yarn 1 is considered deprecated and contains bugs that were only fixed in newer major versions. The sooner plugin devs move away from it the better.
Test scaffold and CI checks repo.
Test PR for gh workflows.
Test release gh workflows
This does not affect
create-plugin update
command.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
📦 Published PR as canary version:
Canary Versions
✨ Test out this PR locally via: