deploy error
[Region: us-west1]
==============
Using Nixpacks
==============
context: 916987557f9b04cf0f6c8046a1d0b305
╔════════ Nixpacks v1.20.0 ═══════╗
║ setup │ nodejs_18, npm-9_x ║
║─────────────────────────────────║
║ install │ npm ci ║
║─────────────────────────────────║
║ build │ npm run build ║
║─────────────────────────────────║
║ start │ npm run start ║
╚═════════════════════════════════╝
#0 building with "default" instance using docker driver
#1 [internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.0s
#2 [internal] load build definition from Dockerfile
#2 transferring dockerfile: 2.45kB done
#2 DONE 0.0s
#3 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1702339400
#3 DONE 0.2s
#4 [stage-0 1/10] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1702339400@sha256:1a9c1eed040aacf8f898be048210ef2d3366b1228373c4e6818362bb75611b32
#4 DONE 0.0s
#5 [internal] load build context
#5 transferring context: 13.54MB 0.1s done
#5 DONE 0.1s
#6 [stage-0 3/10] COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix
#6 CACHED
#7 [stage-0 2/10] WORKDIR /app/
#7 CACHED
#8 [stage-0 4/10] RUN nix-env -if .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix && nix-collect-garbage -d
#8 CACHED
#9 [stage-0 5/10] COPY . /app/.
#9 DONE 0.1s
#10 [stage-0 6/10] RUN --mount=type=cache,id=s/c12cbefb-61b4-42f0-87ac-b313c8c28451-/root/npm,target=/root/.npm npm ci
#10 0.632 npm
WARN config production Use
--omit=dev instead.
#10 37.5416 Replies
Project ID:
c12cbefb-61b4-42f0-87ac-b313c8c28451full build logs please - https://bookmarklets.up.railway.app/log-downloader/
do you use yarn or npm locally?
npm
send me your package.json please
if you use npm locally then you need to use npm in the scripts too
but you use yarn a bunch
omg im an idiot im sorry
no worries
aight changed it and its still doing the same thing
should i send the build log again?
yes
just the command
npm isn't a drop in replacement for yarn in this context, you need to use npm run to run scriptsyeah just changed that rerunning the deploy now
i had never used yarn thought the run was still there
seems to be getting through now
thank you
no problem!