CONTRIBUTING mentions `yarn link`, which doesn't even exist anymore

🐛 Bug Report

CONTRIBUTING.md tells us we can test the project by using yarn link. Unfortunately, yarn has been forced to a random commit of yarn 2, and yarn 2 doesn’t even have the yarn link (no-args) syntax:

faux@astoria:~/clone% yarn --version
1.22.10

faux@astoria:~/clone% cd jest
faux@astoria:~/clone/jest% yarn --version
2.3.3-git.20201026.e34bf6c6

faux@astoria:~/clone/jest% yarn link
Unknown Syntax Error: Not enough positional arguments.

$ yarn link [-A,--all] [-p,--private] [-r,--relative] <destination>

(Also, top tip to save anyone else an hour of debugging: this yarn version ignores your ~/.npmrc, you must rewrite it for them.)

If you use the yarn 2 syntax instead, you instead get a resolution error about @yarn/test-utils, which does indeed not exist in the registry, and apparently yarn isn’t smart enough to link it, either in --all mode or while trying to link just the cli (exactly the same output).

my-app% ~/clone/jest/.yarn/releases/yarn-sources.cjs link ~/clone/jest --all
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error: No candidate found for @jest/test-utils@npm:^26.0.0
    at ~/clone/jest/.yarn/releases/yarn-sources.cjs:2:335032
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
[...]

Expected behavior

Can someone who understands this yarn setup please update the CONTRIBUTING.md document with how to … run jest from git?

[SimenB]

yarn link sorta painful though as the yarn version is checked into this repo, so you need to launch the yarn from here but in the other CWD. Ditching the link instructions altogether seems easier?

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.