Overview

This issue focuses on adding Bun runtime compatibility.
The core development remains in Deno; no Bun-specific configuration files or build systems will be introduced.
Bun support will rely on the same Deno-built artifacts distributed for Node.

Motivation & Benefits

Bun provides performance advantages and growing ecosystem support.
Ensuring compatibility helps developers seamlessly migrate or evaluate runtime options while keeping development unified in Deno.

Use Case

• Running the library in Bun-based servers or scripts.
• Leveraging Bun’s speed and native TypeScript runtime for testing or prototyping.
• Integrating into Bun monorepos using Node-compatible builds.

Proposed Solution (include Next Steps)

• Reuse the Node-compatible ESM output for Bun.
• Avoid committing Bun-specific files (e.g., bunfig.toml).
• Validate that Bun’s runtime correctly resolves imports and APIs.
• Add optional Bun runtime tests to CI for verification.

Alternatives Considered

• Offer a Bun adapter or compatibility layer, but do not diverge from the Deno-centric workflow.
• Document known limitations if any APIs behave differently on Bun.

Related issues

No response

Checklist

• I have searched existing issues
• I have read relevant documentation
• I can contribute to this feature