#Builds failing suddenly

24 messages · Page 1 of 1 (latest)

languid sun
#

I have done some changes and suddenly builds are failing.
Thought this was due to changes i have pushed but I have redeployed a previous build and the error still occurs.
In the image I did a build 21 hours ago, that was successful. I have done a redeploy of the same build at the end showing 15 minutes ago and the build fails too

hallow mantleBOT
#

Project ID: 4f4f01e5-e5da-4e74-9885-a528f14bc4da

languid sun
#

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

sage raft
languid sun
#

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

sage raft
#

do you have a nixpacks.toml file?

languid sun
#

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

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

sage raft
#

do you have a yarn lock file

languid sun
#

i have a package-lock.json

sage raft
#

do you use yarn or npm locally?

languid sun
#

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

languid sun
sage raft
#

please delete your nixpacks.toml file

languid sun
sage raft
#

you have conflicting peer dependencies, please fix that

languid sun
#

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

sage raft
#

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

languid sun
#

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

#

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

#

Thanks1010