10 months ago
I've noticed that sometimes dependencies in package.json specified via catalog:foo will fail at build time (it'll try to resolve the dependency as a remote git repo, which isn't the expected behavior).
I'm using Bun 1.2.2 as the base Docker image, so it should work out of the box.
5 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Bun build fail with no dependencies
- 🧵 Issue with Deploying Discord Bot on Railway – ModuleNotFoundError: No module named 'discord'
- 🧵 Build keeps failing
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
Hello! Have you tried using the Railpack builder? I believe it has better support for bun.
Railway might also have a hard time detecting which package manager you are using if not properly specified as well, try adding this to your package.json if the previous solution doesnt work:
```
{
"packageManager": "bun@1.2.2"
}
```
10 months ago
Bun added support for catalogs in v1.2.14. Updating the image to use Bun >= v1.2.14 should fix this issue. Before adding support for catalogs, Bun would unfortunately see them as git dependencies and attempt cloning them.
9 months ago
Awesome — thank you!
9 months ago
Dang, I added "packageManager": "bun@1.2.2" to every package.json file - no luck.