Can't seem to install an existing project without --legacy-peer-deps
The project was working well, but on a new commit, it started throwing errors on lock files.
I matched the node version and npm version with the one on railway.
I am using NX + nix
53 Replies
Project ID:
N/A
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
Railway
Railway
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
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
Railway
Railway
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
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/
GitHub
GitHub - gitroomhq/postiz-app: šØ Schedule social media posts, measu...
šØ Schedule social media posts, measure them, exchange with other members and get a lot of help from AI š - 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 ā nodejs_20, npm-9_x, 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
https://github.com/gitroomhq/postiz-app/commit/f10bdbccea6fd99c954329569001484518f8ac14I 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
https://github.com/gitroomhq/postiz-app/pull/440
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