Using bun

[RobinTail]

No description provided.

[RobinTail]

Here is what I found out so far about bun:

1. It is fast
2. Benchmarking tool is not yet implemented: Implement a custom benchmark runner oven-sh/bun#6201
   a. Using bunx to run vitest bench and it stucks in CI for some reason.
   b. Fixed it by removing --bun from bunx, so it means that vitest relies on Node env for benching.
3. Code coverage reports (lcov) are not yet implemented: Implement an lcov coverage reporter for bun test oven-sh/bun#4015

[github-actions]

Performance benchmark

5e6ef1d

┌─────────────┬─────────┬─────────┬────────┬───────┐
│             │ 10      │ 100     │ 1000   │ 10000 │
├─────────────┼─────────┼─────────┼────────┼───────┤
│ Performance │ 6174710 │ 1094907 │ 127954 │ 15022 │
└─────────────┴─────────┴─────────┴────────┴───────┘

[RobinTail]

Another thing I found out about bun build:

error: Formats besides 'esm' are not implemented

No dedicated issue, only mentioned roadmap:
oven-sh/bun#159

[RobinTail]

And another issue - no DTS generation supported by bun build
oven-sh/bun#5141

[RobinTail]

Another issue, link:./.. directive seems to be not handled correctly in package.json dependencies by bun.
Should use bun link I think

[RobinTail]

this somehow breaks dependency resolutions when running vitest

[RobinTail]

hanging vitest may be fixed in 2.0
vitest-dev/vitest#5047

[RobinTail]

Not fixed.
with --bun - hanging
without --bun can not find dependency

[coveralls-official]

coverage: 100.0%. remained the same
when pulling fa60065 on try-bun
into 6aeebf3 on master.

[RobinTail]

Last issue — the generated DTS lacks JSDoc.
Related issues:

• Preserve JSDoc ryoppippi/bun-plugin-isolated-decl#14
• transformer: JSDoc comment is missing when using isolatedDeclaration oxc-project/oxc#3906

[coveralls-official]

coverage: 100.0%. remained the same
when pulling ec61604 on try-bun
into 4994008 on master.

[RobinTail]

✅ QA passed