Do not use 'corepack' please, init failed in latest version

[g-mero]

◒ Installing dependenciesD:\softs\coding\NodeJS\node_modules\corepack\dist\lib\corepack.cjs:21535
if (key == null || signature == null) throw new Error(Cannot find matching keyid: ${JSON.stringify({ signatures, keys })});
^
Error: Cannot find matching keyid: {"signatures":[{"sig":"MEQCIF8wLt2fTapHp1XuLDM6OxtNBiZuqsGalvL73sUfv6jzAiAEoXccDEYW0uPydGuU7rRXDs8oK31olzRSrRz8J5a6Vw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"keys":[{"expires":null,"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","keytype":"ecdsa-sha2-nistp256","scheme":"ecdsa-sha2-nistp256","key":"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg=="}]}
at verifySignature (D:\softs\coding\NodeJS\node_modules\corepack\dist\lib\corepack.cjs:21535:47)
at fetchLatestStableVersion (D:\softs\coding\NodeJS\node_modules\corepack\dist\lib\corepack.cjs:21553:5)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async fetchLatestStableVersion2 (D:\softs\coding\NodeJS\node_modules\corepack\dist\lib\corepack.cjs:21672:14)
at async Engine.getDefaultVersion (D:\softs\coding\NodeJS\node_modules\corepack\dist\lib\corepack.cjs:22298:23)
at async Engine.executePackageManagerRequest (D:\softs\coding\NodeJS\node_modules\corepack\dist\lib\corepack.cjs:22396:47)
at async Object.runMain (D:\softs\coding\NodeJS\node_modules\corepack\dist\lib\corepack.cjs:23102:5)

Node.js v22.13.1
│
■ Failed to initialize Ultracite configuration: corepack pnpm add --workspace-root -D ultracite@5.1.9 failed.

[haydenbleasel]

Interesting, I can't repro that. What version of Node are you running?

[g-mero]

Node.js v22.13.1

That's a very common issue with Corepack 0.30.0. Upgrading to the latest version of Corepack solves it, but the upgrade process is a bit annoying since Corepack is now bundled with Node.js. In some cases, you may need to reset global variables or remove the existing binary before upgrading via npm add -g.

[haydenbleasel]

Okay gotcha. We're using nypm to handle package manager commands, so I'll have to investigate more there.

[srejitk]

Facing the same issue here. Running node v20.15.1 .

Fixed it at my end by shifting to node 22