18 mins???

This looks like the build is spending time on the Playwright/Chromium install step, not really your app code.

From the screenshot, you have:

npm ci --omit=dev && npx playwright install-deps chromium ...

and then another RUN npm ci right after it. So first thing I would do is remove the duplicated npm ci, because you're paying that cost twice.

Also, playwright install-deps chromium installs OS packages only. If your app actually needs Chromium at runtime, use:

npx playwright install --with-deps chromium

If this is in a Dockerfile, split the steps so you can see exactly which one is hanging:

RUN npm ci --omit=dev

RUN npx playwright install --with-deps chromium

If it still sits there for 20+ min after reaching 100%, cancel that deploy and try again with the simplified Dockerfile. Btw, this does not look like a Railway routing issue yet, it's still in the image build phase.

It does not look like npm ci alone is stuck. Your Dockerfile appears to run npm ci twice, and one of the steps also runs:

npx playwright install-deps chromium

That command can take a long time because it installs OS-level browser dependencies.

I would simplify the Dockerfile so npm ci only runs once, and install Playwright/Chromium dependencies in a separate clear layer. Also make sure you are not running both:

npm ci --omit=dev

and later:

npm ci

unless you intentionally need two separate stages.

If this is a Playwright app, consider using the official Playwright Docker image instead, since it already includes the browser dependencies.

I'm seeing the same thing in GitHub actions. Playwright downloads 100%, and then everything just locks up. It just sits there and nothing more happens. Have to cancel the workflow and retry. Sometimes multiple times.

I have a PR here on my own repo where I'm trying to cache the download to see if that'll help https://github.com/cedarjs/cedar/pull/1835

clean up your cache and retry. could you show the building logs ?