BladyTancerz
WWasp
•Created by BladyTancerz on 4/22/2025 in #🙋questions
Railway deploy server code fails with ENOENT error, following opensaas and wasp lang docs
I am getting this error when deploying to Railway by following 16.0 docs:
✔ Generated Prisma Client (v5.19.1) to ./../../../node_modules/@prisma/client in 295ms
Start by importing your Prisma Client (See: http://pris.ly/d/importing-client)
Tip: Want to turn off tips and other hints? https://pris.ly/tip-4-nohints
[server-builder 10/11] RUN cd .wasp/build/server && npx prisma generate --schema='../db/schema.prisma' ✔ 2s
[server-builder 11/11] RUN cd .wasp/build/server && npm run bundle
[email protected] bundle rollup --config --silent[!] Error: Could not load /app/.wasp/out/sdk/wasp/dist/server/index.js (imported by src/server.ts): ENOENT: no such file or directory, open '/app/.wasp/out/sdk/wasp/dist/server/index.js' Error: Could not load /app/.wasp/out/sdk/wasp/dist/server/index.js (imported by src/server.ts): ENOENT: no such file or directory, open '/app/.wasp/out/sdk/wasp/dist/server/index.js' ✕ [server-builder 11/11] RUN cd .wasp/build/server && npm run bundle process "/bin/sh -c cd .wasp/build/server && npm run bundle" did not complete successfully: exit code: 1 Dockerfile:42 ------------------- 40 | RUN cd .wasp/build/server && npx prisma generate --schema='../db/schema.prisma' 41 | # Building the server should come after Prisma generation. 42 | >>> RUN cd .wasp/build/server && npm run bundle 43 | 44 | ------------------- ERROR: failed to solve: process "/bin/sh -c cd .wasp/build/server && npm run bundle" did not complete successfully: exit code: 1 It works perfectly fine locally, I have no idea why wasp does not generate the missing files on build? I am using latest wasp cli as well. Any hints?
14 replies