chore: migrate to nodeLinker: node-modules#847
Conversation
|
The actual version of Node.js selected by the GitHub Actions runner is randomly 24.14.1 or 24.15.0 during the current ubuntu-24.04 rollout. As luck would have it https://github.com/nodejs/corepack/actions/runs/25918361425/job/76180620903?pr=847 executed the |
|
#817 had been approved (but closed by mistake I assume) |
Thanks for merging! #817 was intentionally closed, as I explained in the comment #817 (comment). GitHub did not allow me to re-open it (probably because I'd deleted the branch) and in any case the description in #817 was outdated, so I re-wrote it in a much simpler form for this PR. |
Situation
corepack yarn lintfails with Node.js 24.15.0 LTSNode.js 24.15.0 is currently rolling out in
ubuntu-latest, so failures are sporadic.The corresponding upstream issue yarnpkg/berry#7106 is unresolved.
Change
Migrate the
nodeLinkerconfiguration setting from its default value to an explicitnode-modulessetting in a new .yarnrc.yml settings file:nodeLinker: pnpnodeLinker: node-modulesTo achieve this, cherry-pick 22a3fc0 from PR #652 originally submitted by @geigerzaehler.
The setting has no effect on the npm module published as corepack to the npm registry, apart from allowing the CI job
chore("Testing chores") to succeed under Node.js >=24.15.0. ThenodeLinkersetting is not part of the published npm module.Verification
On Ubuntu 24.04.4 LTS, with Node.js 24.15.0 LTS, execute:
corepack yarn install corepack yarn build corepack yarn typecheck corepack yarn lint corepack yarn testConfirm no errors and all tests passing.