a year ago
at first i was using node 20 in my computer but when i deployed the api i didn't get any error from railway but the link takes me to an error page , and then i remembred that i had an error when i deployed my sveltekit app because node 18 that is installed in the server in not compatible with canvas version so i wanted to check by changing the node version to 18 , and i had an error in my machine too this time , but the solution was to just delete node_modules folder and reinstall it , so when redeployed the files (package.json / package-lock.json and index.js) i had this error :ERROR: failed to solve: process "/bin/bash -ol pipefail -c npm ci" did not complete successfully: exit code: 1
ⓘ Deployment information is only viewable by Project members and Railway admins.
4 Replies
a year ago
Try making a new lockfile:
Delete your current
package-lock.jsonandnode_modules/Ensure you are using the correct node.js version you want
Run
npm installto get a fresh package-lockDeploy those changes to railway
No guarantees, just sounds like lock is likely mangled from bouncing back and forth between node versions
a year ago
i deleted them and then i reinstalled them , there is no error in console , but the api link opens a railway page named server error with message Application failed to respond , so i thought maybe the problem is from my code , so i deleted it all and i just kept a get endpoint , and i'm having the same problem , it's not because i'm not using cors right?
a year ago
Hard for me to say without a lot more context. Make sure you have the Railway networking docs open while you're setting up to be sure that's all right. But I agree that the problem is probably in your code. so glhf o7
a year ago
Would be worth it to look at these docs -