Corepack, and the package manager version in the repo

Two developers on different package manager versions produce lock file churn that looks like a real diff and is not.

{
  "packageManager": "[email protected]"
}

// with corepack enabled, the right version is used
// automatically — including in CI
$ corepack enable
$ pnpm install     // downloads 8.6.12 if needed

One line in package.json removes an entire category of “works on my machine”, and the version is now reviewable in the pull request that changes it. Corepack has to be enabled on each machine and in CI, which is one command and is the step that gets forgotten — a check that asserts the running version matches the field is worth the four lines.