ffc857dc-5b3e-47b0-828b-5f9eb466a1d7

?

copied from your build logs -

Fix the upstream dependency conflict

there are many online tutorials on how to fix dependency conflicts, please look into that

in the internet i found --legacy-peer-deps while make npm i, but how i can do it if railway doing it by itself

do you have no interest in fixing the issue properly?

i am interested but i can't

why's that?

I found "--legacy-peer-deps " in internet, but the service itself does "npm i" only , but i need npm i "--legacy-peer-deps " to make my application run

that would not be a proper fix and could cause unexpected issues down the line, have you tried to fix the dependency issues properly?

i fixed it with adding variable NPMCONFIGLEGACYPEERDEPS to true in railway. thanks chatgpt 😁

that's not a proper fix 🫤

i fixed problem properly then.

you have?