Replace Yarn PnP w/ Yarn 2
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 433
- Forks
- 28
- Avg merge
- 48m
- Merged PRs (30d)
- 6
Description
Since Yarn 2 has PnP enabled (with a better implementation as Yarn 1), I think it would make more sense to use that.
To use Yarn 2, the following command has to be run within the project outside of the benchmark:
yarn policies set-version berry
Some other particularities:
-
to remove the cache, better use
yarn cache clean --all. You also can addenableGlobalCachewhich will use a unique cache (otherwise it'll have a first global cache, then a per-project cache). -
when removing the n_m, you'll instead want to remove the
.pnp.jsfile for PnP (I think it's currently marked as n/a)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the benchmark's current Yarn 1 and Plug'n'Play setup, then run yarn policies set-version berry from the project outside the benchmark as described. Check the cache-cleaning and dependency-removal behavior, including .pnp.js; done means the benchmark uses Yarn 2 with the documented PnP workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100