Failed to deploy Nuxt
garage71cl
HOBBYOP

a month ago

Failed to deploy a Nuxt website. It is deployed on Netlify without problem, but I would like to host it on Railway. These are the details:

  • Deployment IDs: 2d6e02b7-fb45-490c-ad2c-3e80fa53c144 and 3c097817-1fdd-449b-ab82-fea84c8aa1ad
  • Service: pendientes
  • Issue: Metal builder terminating before build starts (no Railpack plan, no build logs beyond "scheduling build")
  • Repo: andresvo/pendientes on main branch
$10 Bounty

3 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 1 month ago


a month ago

Are you sure there's no build logs?

I also often deploy Nuxt apps and I've noticed it randomly errors out at build time, doing a simple Cmd/Cntrl + K -> Deploy latest commit fixes it.

I'm gathering more info on this before opening an issue on the Railpack repo.


garage71cl
HOBBYOP

a month ago

This is the build log:

npm ci

1s

npm warn config production Use --omit=dev instead.

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: esbuild@0.27.7 from lock file

npm error Missing: @esbuild/aix-ppc64@0.27.7 from lock file

npm error Missing: @esbuild/android-arm@0.27.7 from lock file

npm error Missing: @esbuild/android-arm64@0.27.7 from lock file

npm error Missing: @esbuild/android-x64@0.27.7 from lock file

npm error Missing: @esbuild/darwin-arm64@0.27.7 from lock file

npm error Missing: @esbuild/darwin-x64@0.27.7 from lock file

npm error Missing: @esbuild/freebsd-arm64@0.27.7 from lock file

npm error Missing: @esbuild/freebsd-x64@0.27.7 from lock file

npm error Missing: @esbuild/linux-arm@0.27.7 from lock file

npm error Missing: @esbuild/linux-arm64@0.27.7 from lock file

npm error Missing: @esbuild/linux-ia32@0.27.7 from lock file

npm error Missing: @esbuild/linux-loong64@0.27.7 from lock file

npm error Missing: @esbuild/linux-mips64el@0.27.7 from lock file

npm error Missing: @esbuild/linux-ppc64@0.27.7 from lock file

npm error Missing: @esbuild/linux-riscv64@0.27.7 from lock file

npm error Missing: @esbuild/linux-s390x@0.27.7 from lock file

npm error Missing: @esbuild/linux-x64@0.27.7 from lock file

npm error Missing: @esbuild/netbsd-arm64@0.27.7 from lock file

npm error Missing: @esbuild/netbsd-x64@0.27.7 from lock file

npm error Missing: @esbuild/openbsd-arm64@0.27.7 from lock file

npm error Missing: @esbuild/openbsd-x64@0.27.7 from lock file

npm error Missing: @esbuild/openharmony-arm64@0.27.7 from lock file

npm error Missing: @esbuild/sunos-x64@0.27.7 from lock file

npm error Missing: @esbuild/win32-arm64@0.27.7 from lock file

npm error Missing: @esbuild/win32-ia32@0.27.7 from lock file

npm error Missing: @esbuild/win32-x64@0.27.7 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 error A complete log of this run can be found in: /root/.npm/_logs/2026-07-15T21_58_44_118Z-debug-0.log


a month ago

There's a mismatch between package.json and package-lock.json file

You have to open your local project, delete the package-lock.json file, then run npm install, push the changes and deploy, this should fix it because it will automatically regenerate the lock file


Welcome!

Sign in to your Railway account to join the conversation.

Loading...