npm run build

22 days ago

copy /etc/mise/config.toml, /usr/local/bin/mise, /mise/installs, /mise/shims, /root/.local/state/mise cached

0ms

copy / /app, .

285ms

npm run build -w @esgnavigator/web

422ms

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

npm error No workspaces found:

npm error --workspace=@esgnavigator/web

npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-30T19_07_20_788Z-debug-0.log

Build Failed: build daemon returned an error < failed to solve: process "sh -c npm run build -w @esgnavigator/web" did not complete successfully: exit code: 1 >

$20 Bounty

1 Replies

Railway
BOT

22 days 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 Railway 22 days ago


i-smuglov
FREETop 5% Contributor

22 days ago

This means npm cannot detect your workspace configuration at build time.

Root causes (most likely)

  1. package.json with workspaces is missing in the container
    • Either not copied
    • Or copied after the build step
    • Or located in a different directory than expected
  2. Wrong working directory
    • The build runs in /app, but your monorepo root may not be there
  3. Workspace name mismatch
    • @esgnavigator/web must exactly match the name field inside that package
  4. Using npm without proper workspace setup
    • npm requires "workspaces" defined in root package.json

Welcome!

Sign in to your Railway account to join the conversation.

Loading...