a month ago
Here's my deploy log:
2026-06-11T17:34:12.058220660Z [err] npm warn config production Use `--omit=dev` instead.
2026-06-11T17:34:12.058225844Z [inf]
2026-06-11T17:34:12.058230199Z [inf] > recipe-app@0.1.0 start
2026-06-11T17:34:12.058234780Z [inf] > node build
2026-06-11T17:34:12.058239195Z [inf]
2026-06-11T17:34:12.058244371Z [inf] Listening on http://0.0.0.0:8080
2026-06-11T17:34:12.181550409Z [inf] Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/d38e31f1-0b30-4cc5-ab3f-a118a29d34a7/vol_g1cchmzio4d8c6fw
2026-06-11T17:34:12.181571330Z [inf] Starting Container
I'm assuming the err is causing the problem. I have tried a few ways to get rid of the error with no luck, including NPM_CONFIG_OMIT="dev"
10 Replies
a month ago
Your logs show that you app had a successful start (listening on port 8080) and that the container started, the crashing must be happening after those lines (which you trimmed)
a month ago
Does it works locally?
It works perfectly, just that on every deploy I get a Deployment crashed email.
a month ago
What is your start command?
a month ago
Try this:
a month ago
You could add a custom Railpack setup or a Dockerfile setup to avoid these issues, but good to know you solved it.
a month ago
Anything else before the thread is marked as solved?
Status changed to Solved 0x5b62656e5d • 25 days ago