a year ago
Hello Railway Team,
I'm facing severe issues deploying my Next.js app on Railway. The deployment fails due to numerous type errors and dependency conflicts, making it impossible to proceed. Despite multiple attempts to fix the issues, the platform does not seem compatible with my setup.
Since I'm unable to use the service as intended, I kindly request a refund. Please let me know the next steps.
Thanks,
Kushal
28 Replies
a year ago
You can always make requests for refunds here:
(Billing History -> Refund)
a year ago
I can try to help you, although I've never deployed a nextjs app before
first let's just get on the same page
are you building with nixpacks or docker?
yeah, also i have created my own docker file in project but that didn't worked
a year ago
makes sense, perhaps you're using a different node version than Railway does
what node version does your app use?
a year ago
so you're using node 23.8?
a year ago
Seems NextjS 15.1.17 needs NodeJS 18.18 and above
Nixpacks support Node 16, 18, 20, and 22 (although only major versions can be specified)
so are you using node 22 then?
a year ago
Do you have that specified in your package.json ?
I tested on Ubuntu, and it works fine. I'm new to your platform and have zero knowledge about it, but I'm experiencing issues with Railway.
a year ago
yea i get that 😔 sorry that you're having trouble
but, do you have your node version specified in your package.json ?
a year ago
oh alright, let me check nextjs docs rq
a year ago
ah I see, it only auto generates it when you create next-app
a year ago
in that case it's safe to alter it
a year ago
if you're using Node 22 locally, then you'll want to add this to your package.json
{
"engines": {
"node": "22"
}
}This will tell Railway that it should build your appllication in a node 22 environment
a year ago
make sure you are actually using node 22 locally though, you can do that by running node -v in the command line
a year ago
awesome! happy I could help 🙂