a year ago
Sometime within the last few hours deploying with bun on Railway has broke.
I went to deploy a new service and initially got this error "bun: command not found" right away. I went to test it by redeploying an existing service (successfully build a couple hours ago with the exact same Railway config / git commit) and it wont even reach the build process with the same error.
7 Replies
Newly deployed service: 81b365cf-c781-4ac1-ac43-bfd80799e996
Service that worked a couple hours ago with the same config and commit: 47b7bbe6-a4bb-43c1-a8f5-d67656794851
Also, there is only 1 single bun lockfile in the root of my project, no other lockfiles
a year ago
Hello,
Looks like you unknowingly have your packageManager field in your package.json set to npm.
We previously didn't support this syntax, but we do now, so npm is being used now instead of bun.
If you would like to switch back to bun, you can set that field's value to bun.
a year ago
no problem!
a year ago
!s
Status changed to Solved brody • about 1 year ago