Railway not using Node v18.16
Hi Railway team,
Fan of the platform. But facing a problem I specified the following:
But Railway insists on using on using
18.12.1 (showing the warning that I get on the build phase)
How can I make it use the version I'm specifying? I'd also like to use v19 in another project.
Thanks.
19 Replies
Project ID:
N/AN/A
if you need a specific minor version of node 18 it might be best to build with a dockerfile
is there any other option @Brody ? I don't want to mess with Dockerfiles.
The reason why I need to update is that I rely on timezone data being current, and it's out of date in the current version for Mexico so it's breaking my app
I don't need a minor version I need 18.16
the 16 part of 18.16 is the minor part of the version
nix packages only has 18.14.1 on the stable channel, and nixpacks isnt using the current nix packages archive, so dockerfile is the way to go
if i could see your repo i could maybe write you up a simple set and forget dockerfile
Thanks for the help. The repo is private because it's a live SaaS with 200+ customers. I could invite you to it, or provide any extra info here that will help you.
I was also told at some point that I could create a file called nixpacks.toml and put something like this inside:
But not sure what commit to use or if it will work
are you on the teams plan?
By using that commit
53dad..... I managed to get node to 18.15.0
Not sure where to find the commit that will include further versions like 18.16
are you a part of a team?
No it's just me
you are using railway for commercial purposes, you would need to be on a teams account, then once you upgrade you can ask a railway engineer
I didn't know
thank you!
kinda misleading name since one person doesn't make a team, but its just the rules for commercial use of the platform π
Flagging this thread. A team member will be with you shortly.
Hey @rickitan - If you don't mind me asking, what pkg depends on that node version?
fix-day-js
Hi Angelo, pkg as NPM module?
Any date package that doesn't include Timezone data (e.g Luxon and Dayjs) will parse the wrong time on Mexico. Because they rely on the underlying OS Timezone data.
If you do
process.versions.tz on the default node version you get from Railway 18.12.1 it returns 2022e which is missing the timezone update from mexico that was introduced in 2022f
@angeloI figure- lemme engage JR here