Hey there! We've found the following might help you get unblocked faster:

• 🧵 cant build react project, need more updated node version

• 🧵 Railway Cli Giving strange error whenever I try to login or view logs

• 🧵 Need Help deploy Strappi project

If you find the answer from one of these, please let us know by solving the thread!

Also experiencing this, unfortunately (us-east-4)

I just try again today but still fail. Anyone get this too?

Could y'all please open an issue on the Railpack GitHub repo? We've got someone who can look at this this week

github.com/railwayapp/railpack

I've created new issue on Railpack but do you have any idea to hot fix it or work around for now? Because i really need to deploy. Thanks.

You can try setting the properties to manually define your yarn version

see the railpack docs at https://railpack.com/

I'm also currently experiencing the same issue.

I just resolved it just by change to using pnpm. Waiting support is hopeless.

I have the same error, please look into it when possible.

Thanks!

Hey, I am sure they will resolve it to the earliest. Whenever I had technical issues in the past, Railway's support team has been very helpful. Let's be patient and give them some time to inspect the issue

A reproducible environment (aka opensource GitHub repo) would be super helpful. We've got someone looking into some Railpack issues this week and can defs have a look at this!

changing the builder to nixpack solved the issue for me.

Using Corepack and using Yarn 4 fixed it for me

As mentioned we'll have someone look at this this week. Looks like an upstream issue (Railpack depends on Mise)

Thanks this Worked for me as well.

Hey! I ran into this exact issue and solved it by switching to a Dockerfile approach.

The issue is that Railpack's Corepack is failing to resolve Yarn 1.22.22. While the exact cause it isn't clear, it appears to be related to how Corepack resolves specific Yarn versions -

possibly a compatibility issue or a registry problem.

The Dockerfile solution works because it bypasses Corepack entirely and installs Yarn directly from npm:

# Instead of using Corepack, install Yarn directly via npm

RUN rm -f .yarnrc \

&& rm -f .yarn/releases/yarn-1.22.22.cjs \

&& npm i -g yarn@1.22.22 --force \

&& yarn --version --no-default-rc

Key differences:

1. Direct npm installation: Uses npm i -g yarn@1.22.22, which pulls from the npm registry (where all Yarn versions are available.

2. Removes Yarn config conflicts: Cleans up .yarnrc and any local Yarn releases that might interfere.

3. Uses --no-default-rc: Ensures Yarn ignores any repository-specific configurations that might cause issues

This approach gives you full control over the Yarn installation process and avoids the Corepack version resolution issue entirely. Plus, you get the added benefits of Docker caching and more

predictable builds.

Hope this helps others facing the same issue!

Indeed Dockerfile as mentioned above will work. But we will also be having a look at this looks like today, tomorrow, or latest early next week

Any date for fixing this problem? I can't switch to Nixpacks, I'm having problems with Biome. Last week I was able to deploy without any problems with Railpack.

We have someone staffed on this issue as we speak, no date, but actively being resolved.

I'm helping out on this issue! I believe we've fixed it: could you retry any builds and let me know if you are still running into issues?

For those who are interested: it looks like what happened here is the mise yarn backend (asdf, for the current mise version used by railpack) was broken/corrupted for some amount of time. The latest version of mise (which we are updating) uses a different backend to avoid this issue, but the current asdf backend looks to be fixed, so builds that were failing should now work.

Hey Mike, thanks for sorting it out, I just did a build and it's working.

Sweet! Awaiting others to chime in to report a successful fix before we close this out.