10 ms·

As a Bun convert, it's interesting that they felt the need to have a preemptive response for Bun as part of this major release. The response itself seems unconv

by jxi 3y ago

As a Bun convert, it's interesting that they felt the need to have a preemptive response for Bun as part of this major release. The response itself seems unconvincing though: Basically, Bun is a lot faster and simpler, but they think they can catch up. I'm not convinced they can catch up even on speed, and Bun ergonomics are also a lot nicer from the get go.

deliriumchn 3y ago
> Basically, Bun is a lot faster and simpler Funny enough, I got our work project working with yarn berry (whatever number this was this summer) in 10-15 minutes, but I couldn't manage to do the same with bun. I'll try again now after they got few minor updates probably just to see if its better now...
- jxi 3y ago
  What didn't work? What was the error?
solardev 3y ago
Were you using Bun on a new project? I tried it on a few existing ones and couldn't get it to build on any of them
- jxi 3y ago
  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.
  - solardev 3y ago
    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).
    - jxi 3y ago
      I use Bun in CI too, and they have a clean GitHub Action for it: https://github.com/oven-sh/setup-bun 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.

by jxi 3y ago

deliriumchn 3y ago

> Basically, Bun is a lot faster and simpler Funny enough, I got our work project working with yarn berry (whatever number this was this summer) in 10-15 minutes, but I couldn't manage to do the same with bun. I'll try again now after they got few minor updates probably just to see if its better now...

jxi 3y ago
What didn't work? What was the error?

solardev 3y ago

Were you using Bun on a new project? I tried it on a few existing ones and couldn't get it to build on any of them

jxi 3y ago
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.
- solardev 3y ago
  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).
  - jxi 3y ago
    I use Bun in CI too, and they have a clean GitHub Action for it: https://github.com/oven-sh/setup-bun 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.