You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 21, 2023. It is now read-only.
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 add enableGlobalCache which 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.js file for PnP (I think it's currently marked as n/a)
JosNun, luxlogica, talentlessguy, dgrant85, some1chan and 5 more
Activity
zkochan commentedon Jan 5, 2020
I don't have objections
omeid commentedon Jan 31, 2020
I would prefer if it was added along with
yarn PnP
than replaced, it should give a better picture of the overall packaging landscape.arcanis commentedon Jan 31, 2020
Not really, the 1.x PnP implem was an experiment branch we never bumped to production. The amount of people who care about that is small.
omeid commentedon Feb 2, 2020
Can you explain what do you mean by bumped to production?
doamatto commentedon Feb 24, 2021
Bumping and +1. Would be great to know if it's worth switching from Yarn 2 from a benchmarking POV