started happening right after upgrading Next, tried a redeploy because the site was responding 502's after the recent incident

is pnpm set as your package manager in your package.json ?

yes, [Region: us-east4]

╭─────────────────╮
│ Railpack 0.15.1 │
╰─────────────────╯

↳ Detected Node
↳ Using pnpm package manager
↳ Found workspace with 10 packages
↳ Installing pnpm@10.18.3 with Corepack

alright, then im out of ideas 💀

will try explicitly setting it in the apps directory, but this has never been an issue in our monorepo before.

Could you try enabling this and let me know how it looks?

explicitly setting in internal apps did not change anything, trying metal build env now

oddly enough started happening in this dev backend environement with no changes, just a redeploy

https://railway.com/project/9cdc7e24-3c32-476b-8599-8003e56a8b36/service/782e8824-d199-4a47-bf01-e65ec48114bc?environmentId=7aae37b2-fee2-4f54-81fd-cfafac01ea5f

yeah no luck

yeah everything i redeploy is having the same issue now

@Error any way to elevate?

Generally a bit at a loss for why this is having the issue so I need to ask internally. Will let you know when I hear back!

okay.

our prod site is down. I convinced my CEO we should move to railway on our last big deployment. I do NOT want to move back to aws 😢

Short term mitigation would be simply using a regular Dockerfile! Gives you a fine level of control over any aspect of the build -> run process.

@Error i just resolved it

when upgrading packages, i changed my .nvmrc to use 25

there must be some bug in railway containers with this node version when using pnpm

Good to know but that is super odd hmmm. I'll note this for later thank you!

going back down to version 22 fixed it.

thanks

@foundnone.eth anything else we can help you with or can we mark this thread as solved?

You can close it thanks