Description

The local setup instructions in CONTRIBUTING.md say pnpm can be installed via Corepack, which "ships with Node.js", then recommend running:

corepack enable

While following the instructions, I used nvm use stable, which selected Node v25.8.0 with npm v11.11.0. In that environment, corepack is not available on PATH:

$ nvm use stable
Now using node v25.8.0 (npm v11.11.0)

$ corepack
-bash: corepack: command not found

This is confusing because the docs say Corepack ships with Node.js, but Node 25+ no longer distributes Corepack with Node. The docs do recommend Node 22 in the nvm snippet, but it is easy to read "v22+" / "ships with Node.js" as applying to the current stable Node release.

Official context:

• build: stop distributing Corepack nodejs/node#57617
• nodejs/node@92428c2609

Expected outcome: the setup docs should make this explicit, for example by saying to use Node 22/LTS rather than stable, or noting that Node 25+ users must install Corepack separately.

Reproduction

1. Install/use latest stable Node via nvm, currently Node 25.x:

   nvm use stable

2. Follow the pnpm setup instructions in CONTRIBUTING.md:

   corepack enable

3. Observe:

   -bash: corepack: command not found

XDS Version

Repository setup documentation on main; package version 0.0.0.

Environment

macOS shell using nvm. Observed with Node v25.8.0 and npm v11.11.0.