Hi there Austin, the error is showing up in your build logs here as that’s where things are failing:

” ⨯ Static worker exited with code: null and signal: SIGABRT”

This looks like it could be a memory issue or related to some packages. Could you please look into the logs to investigate this further?

Here's a couple of suggestions from my end:

• Could you please check if there’s any dependencies you’re not using and prune them out?

• Check if purging dependencies as mentioned here helps: https://stackoverflow.com/questions/76991063/static-worker-unexpectedly-exited-with-code-null-and-signal-sigterm

• Could you see if following the configuration closer to our quickstart guide which uses NextJS helps? https://docs.railway.com/quick-start

Thank you! After tons of digging, the multi-threaded nature of the builder in Railway (compared to Vercel) was causing a race condition at build time. Enforcing a single worker during building fixed the issue for us.

Appreciate the quick reply! This can be closed.