2 years ago
Hello, I ran into a build error for my react app when deploying
ERROR: failed to solve: process "/bin/bash -ol pipefail -c npm i" did not complete successfully: exit code: 1
previous deployments work just fine then out of nowhere all vite react app deployments ran into this issue when building.
please help me with this issue!
31 Replies
2 years ago
hello, can you please scroll further up in the logs so that you can read the error that caused the failed build
2 years ago
what service, and what environment please
2 years ago
please provide this info so i can look at the service
ah okay, do you just need the names of the services and enviroment?
service name: saleshub-web
environment: staging
2 years ago
long shot but can you try to set a NIXPACKS_NO_CACHE variable to 1 please
2 years ago
May I try kicking off a deployment?
2 years ago
are you using node 22 locally?
oh but there is another similar service that is having the exact same issue but with node 20

2 years ago
delete you local node_modules, are you able to run npm i while cd'd into the frontend folder?
it hits this error
npm ERR! Unsupported URL Type "workspace:": workspace:*
2 years ago
locally?
2 years ago
well then it stands to reason if you fix that error you could also fix the failed build on railway
2 years ago
sounds good!
hmm but something im still lost at is why all my other vite react service is having this issue also, seems kinda out of nowhere
For local build i usualy use pnpm, so i dont usually run into this issue, could me using pnpm for the monorepo build is whats causing the issue with npm?
im still having trouble trying to solve why the npm i doesnt go through :/
I tried re deploying a running vite react app set up the same way and the service ran into the same error, even though i didnt change any configs or code
2 years ago
pnpm will be used as long as a pnpm lock file is found
okay, so i did not change anything and did a redeploy and it went through as normal :/ I guess its solved for now
2 years ago
guess it was a transient issue with npm
2 years ago
!s
Status changed to Solved brody • over 1 year ago


