Mind sharing your build logs?
https://bookmarklets.up.railway.app/log-downloader/

[Region: us-west1]

==============

Using Nixpacks

==============

context: 85258cc6ef3560f6fc10057c8c0e8011

╔════════ Nixpacks v1.29.1 ═══════╗

║ setup │ nodejs_18, npm-9_x ║

║─────────────────────────────────║

║ install │ npm ci ║

║─────────────────────────────────║

║ start │ npm run start ║

╚═════════════════════════════════╝

#0 building with "builder-Lyg-" instance using docker-container driver

#1 [internal] load build definition from Dockerfile

#1 transferring dockerfile: 2.55kB done

#1 DONE 0.0s

#2 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1731369831

#2 DONE 0.3s

#3 [stage-0 1/10] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1731369831@sha256:248c718af9f76e602170a3cdbf69658edf55c910023104e1f277e517b77977a0

#3 resolve ghcr.io/railwayapp/nixpacks:ubuntu-1731369831@sha256:248c718af9f76e602170a3cdbf69658edf55c910023104e1f277e517b77977a0 done

#3 DONE 0.0s

#4 [stage-0 2/10] WORKDIR /app/

#4 CACHED

#5 [internal] load .dockerignore

#5 transferring context: 2B done

#5 DONE 0.0s

#6 [internal] load build context

#6 transferring context: 3.55MB 0.0s done

#6 DONE 0.1s

#7 [stage-0 3/8] COPY .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix

#7 CACHED

#8 [stage-0 4/8] RUN nix-env -if .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix && nix-collect-garbage -d

#8 CACHED

#9 [stage-0 5/8] COPY . /app/.

#9 DONE 0.1s

#10 [stage-0 6/8] RUN --mount=type=cache,id=s/709a1afc-6826-4598-9cbc-e82974354f3c-/root/npm,target=/root/.npm npm ci

#10 0.376 npm

WARN config production Use --omit=dev instead.

You need to use the tool I sent you and then upload the file that you get from using it, otherwise I can't see the full build logs

nothing happens when i click the link.
I also went to my service and opened the link from there, but nothing happened again.
This is a screenshot from where im trying to open it.

Alright that screenshot works fine, I can see the issue there, you just need to switch to V2 runtime in your service's settings- you're currently on a legacy runtime

This worked. Thank you for your help. Would have never been able to do it without the guidance.

Awesome! I'm glad it worked, happy I could help