Open darklight9811 opened 6 months ago
I've run in the same issue when trying go use Next.js with Bun in a Docker container for deploy with fly.io in a monorepo setup.
I'll try to isolate a reproduction repository with my use-case w/ Docker.
@wesleycoder I don't know if its the same case as you, but bun 1.1.17 fixed it for me. It was an issue with bun install, if I installed everything with node, it would work when running bun.
I will close it for now since the bug I reported was fixed
Actually the error just reappeared out of nowhere, but a solution for me is to install using yarn and just run dev with bun
related
I managed to fix my issue with the help of turborepo, running the prune
command with the --docker
flag was enough to mitigate most of the problems for me.
For me prune
fits because I was building only a subset of the monorepo, but this may not apply to everyone.
Maybe you can try prune
and see if it helps you, although it seems this occurs in dev mode for you, while for me was only at prod/build time:
https://turbo.build/repo/docs/reference/prune
What version of Bun is running?
1.1.0-canary.58+83a99bf19
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What steps can reproduce the bug?
Use the repo:
Run bun install and them
bun --bun run dev --scope=app
What is the expected behavior?
For the code to run the server and start it
What do you see instead?
A bunch of errors are thrown in the terminal (its trying to log something), but finally throws a:
Additional information
This is a opensource project for an app that helps find missing people and pets