4f4f01e5-e5da-4e74-9885-a528f14bc4da

That is the 'staging' environment build. Have done a redeploy of the prod build that was successful 4 days ago and that is failing too. See below

it's very hard to help with the issue when we aren't told the issue, please provide your build logs with this

Logs

1219662149979345028

I haven't changed any configs recently I just assumed it was a build issue on railway not on my code or any changed railway configs

do you have a nixpacks.toml file?

Yes `[phases.setup]
nixPkgs = ['nodejs', 'yarn']

[phases.install]
cmds=['yarn install']`

do you have a yarn lock file

i have a package-lock.json

do you use yarn or npm locally?

I use npm, am guessing I should change the nixpacks to npm

No, this causes an error 1 minute into build

1219665908121866270

please delete your nixpacks.toml file

Okay done

1219667126655254618

you have conflicting peer dependencies, please fix that

How can i change this command install │ npm ci to something along the line of --legacy peer deps, I only see how to override build command and have the script in

ideally you would properly fix the conflicting peer dependencies, do you not have any interest in that?

Okay, done. First the image size went from 2gb to 500mb after somehow switching to npm, wild. Second the server still does not start <:mildpanic:804271964587819059>

1219676098175045643

I'll take the rest back to Medusa. I think there is an offending plugin

Thanks<:1010:1173874936306221126>

happy to help where i can