Running Sveltekit App inside a monorepo - Build errors - Path not found
I've tried a few different permutations of potential solutions but haven't been able to track down anything that works for me.
I have a project (
3437cb53-716a-4154-9d3b-63def56dd675/service/6ff1c6cf-e318-4926-be63-bfc4720ed8a3
) where I am attempting to build and run a sveltekit app that I have recently moved from it's own repo to a monorepo of mine.
The project is located at $ROOT/projects/thorne-wolf-com/
and I get various errors with various configurations.
Attempt #1
Root Directory: /projects/thorne-wolf-com
, Build Command npm run build
, Start Command node build/index.js
Error: Could not load /app/src/lib/components/ArticlePreview.svelte (imported by src/routes/articles/all/+page.svelte): ENOENT: no such file or directory
Comments: this path does indeed exist but I don't have much visibility into what directory Railway actually clones
Attempt #2
Root Directory: /
, Build Command cd projects/thorne-wolf-com && npm run build
, Start Command node build/index.js
Error: #13 0.303 /bin/bash: line 1: npm: command not found
Comments: I want to specify node as a provider but I can't do it in the root folder of my monorepo because then how do I differentiate my python projects from my node projects. So a root level nix config doesn't help me. Is there an alternative?
Attempt #3
Same as #2 but I specify NIXPACKS_NODE_VERSION=18
in my env variables.
Error: (It installs a bunch of python packages from a separate project) then npm: command not found
Let me know if there is any other info I need to provide for this.5 Replies
Project ID:
3437cb53-716a-4154-9d3b-63def56dd675,6ff1c6cf-e318-4926-be63-bfc4720ed8a3
You might find these helpful:
- Failing to deploy a NestJs api in Railways UI from a Turbo monorepo
- Help migrating Node & Express API from heroku to Railway
- Unable to build app
⚠️ experimental feature
Attempting to use
railway up
from the "Unable to build app" link
#13 0.372 /bin/bash: line 1: cd: projects/thorne-wolf-com: No such file or directory
- probably just need to update build commandnpm: command not found
- but this seems to be from githubrailway up
again and it works but I no longer have https?? (transient issue)
Remaining question is how should I configure my repo to deploy in the same way that railway up
has it deploy?