undefined | Better HN

0 pointsjxi2y ago0 comments

Converted existing large NPM workspace-based projects. It depends which part of Bun you're talking about. Do you mean the package manager didn't work or the runtime didn't work? I would be a bit surprised if the package manager was not a drop-in replacement, but I know they recently fixed a lot of bugs too.

0 comments

2 comments · 1 top-level

solardev2y ago· 1 in thread

Both. This was a while ago (early this year, late last year?). I didn't care about the runtime, but the package manager kept crashing, and I spent a few hours digging through the error logs and trying to fix each error one by one, but never got far enough to actually successfully build my project. (It was just a basic static-file TypeScript app with lots of older dependencies).

I unfortunately don't have the logs anymore. I'd be happy to try Bun again on new personal projects, but I'd be afraid of using it for any real-world work project at this point; the risk of having to spend time debugging it isn't worth the performance improvements (since the packagers are usually just run on CI/CD anyway, and local `next dev` or similar is already fast enough).

jxiOP2y ago

I use Bun in CI too, and they have a clean GitHub Action for it: https://github.com/oven-sh/setup-bun.

Actually now that you mention CI, I remember now that I did also run into non-deterministic problems running type checks on projects with Bun using Github's free runner.

Errors looked like this, but it worked fine every 2/3 runs with the exact same code: `tsconfig.json(5,25): error TS6046: Argument for '--moduleResolution' option must be: 'node', 'classic'.`

It was fixed by just running on my own runners instead, and I never hit those errors building locally. Very weird.

j / k navigate · click thread line to collapse