a year ago
The last log output was an npm warn at 08:52, then the build times out at 09:09. How can I find more info about what caused the build to stall?
I see npm warn messages, but no errors. This build step completes fine and without errors when I run it locally, in much less than the 17 mins it took for this timeout.
Last log entry was "#12 107.5 npm warn deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x."
ⓘ Deployment information is only viewable by project members and Railway employees.
3 Replies
a year ago
With repeated tries the build completes occasionally, but is still unreliable. It can fail mutiple times before passing with the same source code. Still stalls after the same line; the following lines come 10 mins later: "added 2199 packages, and audited 2200 packages in 11m". Does 11 mins indicate too many npm packages for that bundle? It doesn't take that long when I build it locally.
10 months ago
Hi Hannah, did you ever figure out what was causing your issues? I'm running a Vite React App and it's timing out after 20 minutes the majority of the time but sometimes builds fine. Each time I've tweaked the code so I'm not sure if I'm actually having an effect or not.
rickcedwhat
Hi Hannah, did you ever figure out what was causing your issues? I'm running a Vite React App and it's timing out after 20 minutes the majority of the time but sometimes builds fine. Each time I've tweaked the code so I'm not sure if I'm actually having an effect or not.
10 months ago
No sadly not, so I went back to Heroku where I have to pay more. It was the same pattern for me, most often the build timed out but occasionally it built fine, sometimes with no change to the code.