Bun Start Command Not Running
Hi, I'm running a bun project which is not running the run command in the deploy logs.
The first image shows my deploy which is successful. The second photo shows the configs I made to my railway.toml file. At first, it was by default using npm ci since i was transitioning from a node codebase to bun codebase. I actually had to upgrade bun to >= 1.0.2 on my local, since it wasn't working on previous versions due to an outdated promise library that was then patched
. Then I rewrote the railway.toml to use
bun i --no-save
. It was correctly building after that. I tried bun start
and bun run start
, but as you can see in the third photo, my deploy logs are empty.
Is it possible that an older version of bun is running on nixpacks? I saw somewhere that 1.0.8 was being used but im not sure. Also, if that was the case, would I at least get an error in my deploy logs?5 Replies
Project ID:
b67f2a5f-69c5-495d-8fc7-1d8d5e623f46
b67f2a5f-69c5-495d-8fc7-1d8d5e623f46
This screenshot is from a different project, where the first thing that shows up in the logs is the command being run.
Anyone have any ideas?
I've now tried updating nixpacks in my nixpacks.toml with latest version to get newest version of bun and it seems like the deploy just spams bun install over and over again.
Solution
Fixed it by removing "install" script from my package.json somehow