feat: experimental bun and deno support

[Uzlopak]

Checklist

• run npm run test && npm run benchmark --if-present
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[jean-michelet]

Not against it, but I think we don't official support these runtime through the organization right?

[gurgunday]

Not officially, yes, we're Node first

But I think we have an unofficial policy to support other runtimes in a best-effort manner, meaning as long as they don't disrupt anything related to Node (see alternative runtimes job in Fastify, there was some discussion around it with similar conclusions)

[Uzlopak]

@jean-michelet
@gurgunday

Would be cool if there is a review. :)

Pinned swc to 1.20 because of

swc-project/swc#11129

[gurgunday]

Pinned swc to 1.20 because of

swc-project/swc#11129

That was my only question actually

lgtm

[jean-michelet]

Recommend to wait for @fastify/leads feedback.

[Uzlopak]

In #408 @mcollina approved the corresponding changes.

[Eomm]

Does it mean that fastify support it too?
I would mark it as "experimental" feature in case, where experimental means:

• nodejs has priority
• if a feature does not work on another engine, it does not stop the publishing

[Fdawgs]

@Uzlopak Can you please rebase and resolve merge conflicts? I think this is good to go after that!

[Uzlopak]

@Fdawgs

done

[Uzlopak]

@Eomm
I renamed the title and added "experimental". If it is failing for some reason on deno or bun, we are not obligated to "support" it at any cost. If bun or deno workflows fail, we can decide to merge anyway.

[Eomm]

Thanks

I would not scream it to the world, but I know you are cooking something 😄