3 months ago
deployment ID: b0828c7b-e036-4baa-a03c-b32fbb4cbcdb
logs:
RUN npm ci
2s
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@wallet-standard/base@1.1.1',
npm warn EBADENGINE required: { node: '>=22' },
npm warn EBADENGINE current: { node: 'v20.20.2', npm: '10.8.2' }
npm warn EBADENGINE }
npm error code EUSAGE
npm error
npm error npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
npm error
npm error Missing: typescript@5.9.3 from lock file
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm error [--no-bin-links] [--no-fund] [--dry-run]
npm error [-w|--workspace [-w|--workspace ...]]
npm error [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci" for more info
npm notice
npm notice New major version of npm available! 10.8.2 -> 11.17.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.17.0
npm notice To update run: npm install -g npm@11.17.0
npm notice
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-06-21T04_55_41_628Z-debug-0.log
Build Failed: build daemon returned an error < failed to solve: process "/bin/sh -c npm ci" did not complete successfully: exit code: 1 >
6 Replies
3 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 4 months ago
3 months ago
the error says that your package.json and package-lock.json is out of sync, run npm install on your local machine and push the changes to github to sync the lock file
the error also says that @wallet-standard/base require node v22 or newest to work, if you're using railpack (railway default builder), you can simply add RAILPACK_NODE_VERSION=22 to your environment variable to update the node version
3 months ago
can you tell what you are using for deployment railwaypack or connected directly with repo or docker ?
3 months ago
thanks for commenting. I ended up switching to an older version of walletconnect for now. Here's what Grok had to say.
Railway is ignoring the NIXPACKS_NODE_VERSION variable (the log still shows Node 20.20.2). This is a known flaky behavior with some Railway setups.
The real problem
@walletconnect/ethereum-provider@2.23.9 pulls in @reown/appkit, which pulls in @wallet-standard/base@1.1.1 — a package that hard-requires Node ≥ 22. Even with the variable set, Railway's builder isn't respecting it for this repo.
Recommended fix (do this now)
We should switch to a much lighter WalletConnect setup that works on Node 20. This avoids the entire @reown/appkit + @wallet-standard dependency tree.
Plan:
Replace @walletconnect/ethereum-provider with @walletconnect/universal-provider + a small QR modal (or use the official @walletconnect/modal which is lighter).
Regenerate the lockfile under the current Node 20 environment.
Push — Railway will succeed because nothing will require Node 22 anymore.
Would you like me to do this switch right now? It will take ~2 minutes and should make the Railway build pass cleanly.
(Alternative: we can keep fighting Railway's Node version, but it's likely to keep failing.)
3 months ago
i'm going to the club now to have a drink and dance a little. Good night or good morning or good afternoon
carlosreyes0
thanks for commenting. I ended up switching to an older version of walletconnect for now. Here's what Grok had to say. Railway is ignoring the NIXPACKS_NODE_VERSION variable (the log still shows Node 20.20.2). This is a known flaky behavior with some Railway setups. The real problem @walletconnect/ethereum-provider@2.23.9 pulls in @reown/appkit, which pulls in @wallet-standard/base@1.1.1 — a package that hard-requires Node ≥ 22. Even with the variable set, Railway's builder isn't respecting it for this repo. Recommended fix (do this now) We should switch to a much lighter WalletConnect setup that works on Node 20. This avoids the entire @reown/appkit + @wallet-standard dependency tree. Plan: Replace @walletconnect/ethereum-provider with @walletconnect/universal-provider + a small QR modal (or use the official @walletconnect/modal which is lighter). Regenerate the lockfile under the current Node 20 environment. Push — Railway will succeed because nothing will require Node 22 anymore. Would you like me to do this switch right now? It will take ~2 minutes and should make the Railway build pass cleanly. (Alternative: we can keep fighting Railway's Node version, but it's likely to keep failing.)
3 months ago
nix pack is old use railpack. but in my experience always prefer docker for deployment.
carlosreyes0
i'm going to the club now to have a drink and dance a little. Good night or good morning or good afternoon
3 months ago
enjoy