Trying 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

ae67c65

┌─────────────┬─────────┬─────────┬────────┬───────┐
│             │ 10      │ 100     │ 1000   │ 10000 │
├─────────────┼─────────┼─────────┼────────┼───────┤
│ Performance │ 5814819 │ 1006583 │ 125482 │ 14963 │
└─────────────┴─────────┴─────────┴────────┴───────┘

[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 step fails because lcov is not generated by bun test --coverage

[RobinTail]

DTS and CJS should be supported by bun builder in the future

[RobinTail]

Might be a solution at least for DTS:
https://github.com/wobsoriano/bun-plugin-dts

[RobinTail]

no, it does not work well at all

[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

[RobinTail]

Fixed by installing the dependency it could not find