can you link to a deployment when you first saw this issue?

Yes

3f010081-49b8-4c49-bada-565a6ae3ad13

full url link please?

it throws locks error on a deep package json

Like this?
https://railway.app/project/355a123a-8f0d-473a-aa69-318226cfbe58/logs?filter=%40snapshot%3A09eb689c-b351-4aaf-bc69-c1211b1eb5cf+OR+%40replica%3A09eb689c-b351-4aaf-bc69-c1211b1eb5cf&start=1732013452520

to the build that threw the errors

this is the link

that is a link to /logs

of the log explorer of the build

i would prefer a link to the failed build please

Where to click? I click on the number next to "Backend"

copy the url

https://railway.app/project/355a123a-8f0d-473a-aa69-318226cfbe58/service/4748b9a3-63eb-4568-b8c4-225591f355cb?id=3f010081-49b8-4c49-bada-565a6ae3ad13

perfect

so you deleted your local node_modules and ran npm ci locally without issue?

Yes

I don't know if you have time, but it's for my open-source project
https://github.com/gitroomhq/postiz-app/

you can try and run it with npm ci

i did -

so weird

I have a super computer

but railway running
║ setup │ nodejs20, npm-9x, openssl ║

with npm 9

i dont think that matters all too much, its clear i can repro locally with npm 10, so the issue is elsewhere

let me get you the commit im working with

great

f10bdbccea6fd99c954329569001484518f8ac14

I mean, would it be possible to just make a PR

with the package json

created for you?

I can just use that one 😄

since i can repro, you want me to update the lock file and submit a pr?

Only if it's possible, yes

clearly my computer does it wrong

yeah i can do that, let me grab the latest repo, i just grabbed the code from the commit of the deploy you linked

Thank you so much

wow eiter npm is slow or my internet, perhaps both

Thank you so much!

Will add it now 🙂

do your testing please, i did not run the project locally

that's ok, worst case I will revert, the latest docker version will not be updated

oh wow i didnt know vercel did this too

Yeah, I need to remove it, it's annoying 😄

railway does it, and its not removable haha

I think in vercel it's also not removeable only if you disable preview deployments

fair

okay, let me know how it goes!

waiting 😄

so far looks good

i forgot to ask, why vercel, why not run the frontend on railway too?

Honestly, many people pitched me about the advantages of running on vercel with all their special cases how they handle nextjs

with serverless functions and edge

etc…

in railway it will be containerized

is that bad?

Honestly, I don't know

it would be easier to put on railway that's for sure

cheaper probably also

maybe thats a weekend project

it will take me a few minutes to do it with nix

Just not sure about all the pros and cons

it doesnt need to be done with nixpacks, you could do it with a dockerfile

Yay! you commit worked!

awsome!

And I got a new contributor 😎

Thank you so much for all the help

any time! let me know if you face any build errors when you try running the frontend on railway too