v0.25.0 crashes with ENOENT on fresh install

[merceyz]

In a fresh docker container running Corepack crashes with ENOENT

$ docker run --rm -it node:20.11.1 bash -c "npm install -g corepack@0.25.0 && corepack yarn -v"
Internal Error: ENOENT: no such file or directory, open '/root/.cache/node/corepack/lastKnownGood.json'
Error: ENOENT: no such file or directory, open '/root/.cache/node/corepack/lastKnownGood.json'

Git bisect points to #364.

[jhb-dev]

Same issue here. Maybe related to this change in v0.25.0 ?

[merceyz]

Yeah, git bisect points to #364.

[half0wl]

Same issue here on railway.app -- we're seeing a lot of user builds utilizing corepack fail due to this.

Our current workaround is to install the last known good release (0.24.1):

npm install -g corepack@0.24.1

[nikolalsvk]

I'm using railway.app with nixpacks and the fix is to create a nixpacks.toml with this:

[phases.install]
cmds = ["npm install -g corepack@0.24.1 && corepack enable", "pnpm i --frozen-lockfile"]
dependsOn = ["setup"]

I'm using pnpm i --frozen-lockfile but you can replace it with the command of your choice.

[aduh95]

I have a potential fix: #382
If someone could try it out and confirm if it solves the issue, that'd be great.

[ajw725]

we ran into this as well. running corepack install --global <yarn-version> fixes the issue, but we have to run that separately for each user that needs to use yarn.

[ntucker]

Thanks for the quick fix aduh95! I'm wondering since this is breaking many peoples CI - when is the plan to release this? I can't do a workaround for my usage of https://docs.renovatebot.com/ as it is a third party tool that depends on this working.