9 months ago
I'm trying to make my service install node 22 and even though it should be the default and I'm also setting the RAILPACK_NODE_VERSION env var to 22 it still installs Node 18.
I also tried setting the engines.node property in the package.json file to 22 but no luck.
Can you advice what to do?
2 Replies
9 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 lts node 22 outdated
- 🧵 Set Railpack Node Version
- 🧵 railway isn't using the specified node version
- 🧵 Update Node
If you find the answer from one of these, please let us know by solving the thread!
9 months ago
I was able to work around this by adding a dummy script to my package.json file that used node:
"node:version": "node --version"I'd expect that having the env variable set or including node in the engines parameter would also make the container install it but it doesn't. Also the default isn't actually v22.
9 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 9 months ago
Status changed to Solved brody • 9 months ago