18 days ago
I try to deploy a Shopify app from Github and though I use node "node":">=20.0.0" in my engine property I get always an error with this version.
Any idea?
Thx
Here is my log that repeats
[Region: us-west1]
╭─────────────────╮
│ Railpack 0.13.0 │
╰─────────────────╯
↳ Found .dockerignore file, applying filters
↳ Detected Node
↳ Using npm package manager
↳ Found workspace with 1 packages
Packages
──────────
node │ 18.20.8 │ package.json > engines > node (>=18.0.0)
Steps
──────────
▸ install
$ npm ci
▸ build
$ npm run build --workspace=discount-function-js
Deploy
──────────
$ npm run start
Successfully prepared Railpack plan for build
context: xdx5-niOM
load build definition from railpack-plan.json
0ms
copy /mise/shims cached
1ms
install mise packages: node cached
0ms
install apt packages: libatomic1 cached
0ms
copy prisma, .npmrc, package-lock.json, extensions/discount-function-js/package.json, package.json cached
0ms
mkdir -p /app/node_modules/.cache cached
0ms
npm ci
1s
npm warn config production Use --omit=dev instead.
npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: @react-router/dev@7.9.4
npm error notsup Not compatible with your version of node/npm: @react-router/dev@7.9.4
npm error notsup Required: {"node":">=20.0.0"}
npm error notsup Actual: {"npm":"10.8.2","node":"v18.20.8"}
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-11-23T11_28_06_054Z-debug-0.log
ERROR: failed to build: failed to solve: process "npm ci" did not complete successfully: exit code: 1
12 Replies
18 days ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
18 days ago
Are you using Nixpacks? If so, try switching to Railpack and see if this engine error still happens.
18 days ago
Hey there!
I think somewhere in your package.json there is a line which looks something like:
"engines": {
"node": ">=18.00.0"
},Your package.json is imported in Railpack and will override the default v22. You have a package that will only work with node v20 or higher. So you need to find the engine in your package.json and edit that line. After that run npm install to update your package-lock.json and deploy again. This should fix the issue.
18 days ago
Thx all,
but my package.json doesn't contain something like
"engines": {
"node": ">=18.00.0"
},
I use Railpack
I have deleted node-modules and did npm install and the problem persists
itzik-lesher
Thx all,but my package.json doesn't contain something like "engines": { "node": ">=18.00.0" },I use RailpackI have deleted node-modules and did npm install and the problem persists
18 days ago
Hey, that error basically means that one of your packages does not support Node v18 and needs v20 and above. To fix that, specify the following lines at the root of your package.json:
"engines": {
"node": ">=20.0.0"
},After that, Railpack will detect the correct version and the error should go away.
Also, I would recommend using the LTS version (it's the latest and most supported one) if your project supports it. If any issues appears, revert back to the one above.
"engines": {
"node": "24.11.1"
},Let me know if you hit any issues while changing those versions!
18 days ago
I hit the same issue.
I installed the NODE TLS 24.11.1, commited and pushed to GITHUB, than redeployed. Nothing new...
rc, prisma
141ms
npm ci
1s
npm warn config production Use --omit=dev instead.
npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: @react-router/dev@7.9.4
npm error notsup Not compatible with your version of node/npm: @react-router/dev@7.9.4
npm error notsup Required: {"node":">=20.0.0"}
npm error notsup Actual: {"npm":"10.8.2","node":"v18.20.8"}
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-11-23T16_07_55_469Z-debug-0.log
copy /mise/shims, /mise/installs
485ms
ERROR: failed to build: failed to solve: process "npm ci" did not complete successfully: exit code: 1
itzik-lesher
I hit the same issue.I installed the NODE TLS 24.11.1, commited and pushed to GITHUB, than redeployed. Nothing new...rc, prisma141msnpm ci1snpm warn config production Use --omit=dev instead.npm error code EBADENGINEnpm error engine Unsupported enginenpm error engine Not compatible with your version of node/npm: @react-router/dev@7.9.4npm error notsup Not compatible with your version of node/npm: @react-router/dev@7.9.4npm error notsup Required: {"node":">=20.0.0"}npm error notsup Actual: {"npm":"10.8.2","node":"v18.20.8"}npm error A complete log of this run can be found in: /root/.npm/_logs/2025-11-23T16_07_55_469Z-debug-0.logcopy /mise/shims, /mise/installs485msERROR: failed to build: failed to solve: process "npm ci" did not complete successfully: exit code: 1
18 days ago
It still seems that Railpack is forcing the use of NodeJS v18. Is your repository public? If not, can you share your entire package.json file, including the build logs?
17 days ago
My repo is public:
https://github.com/itzik-lesher/flexible-product-discounts
Thx
17 days ago
Any idea?
itzik-lesher
Any idea?
17 days ago
Hey, thanks for the repository link, I managed to do a PR that fixes all the issues that I encountered while deploying (https://github.com/itzik-lesher/flexible-product-discounts/pull/1).
I've removed the
.node-versionfile (Railpack can detect the verrsion by using the engines property)Added Remix vite plugin to
vite.config.jsUsed the correct package on
route.js
If you encounter any other issues please let us know!
passos
It still seems that Railpack is forcing the use of NodeJS v18. Is your repository public? If not, can you share your entire package.json file, including the build logs?
16 days ago
Thx Mr. Passos,
I'm really new to this stuff so forgive me if I ask stupid questions...
Did you mean in the answer that you deployed it yourself or do I have still to deploy?
Do I have to change the repo accord to what you did?
What do I have to do now in order to use the app publicly?
Thx
itzik-lesher
Thx Mr. Passos,I'm really new to this stuff so forgive me if I ask stupid questions...Did you mean in the answer that you deployed it yourself or do I have still to deploy?Do I have to change the repo accord to what you did?What do I have to do now in order to use the app publicly?Thx
16 days ago
You would need to merge the pull request in your repository (as passos has linked).
Your Railway service should automatically redeploy assuming the repository is linked.
