Bun-native test runner support

[truthixify]

Tier: M (2-4 days) Type: test

Context

compat

Scope

Vitest works well in Node but Bun has its own test runner that's faster for CI. Confirm SDK tests run under bun test and add a CI matrix entry.

Acceptance criteria

• Verify all existing tests pass under bun test
• Document any incompatibilities (and fix where possible)
• Add bun-tests job to CI
• Note: vitest stays the primary runner; bun is supplemental

Files to start with

• Tests pass under both vitest and bun test
• CI matrix expanded
• Compatibility notes documented

Why this matters

• package.json
• .github/workflows/ci.yml

[frank0277]

@frank0277 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi i would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @frank0277 to this issue.

[Mathew2k-hash]

@Mathew2k-hash has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd like to work on this issue because cross-runtime compatibility improves the SDK's reliability and developer experience. Verifying support for both Vitest and Bun helps catch environment-specific issues early while providing faster testing options for CI.

I'll validate the existing test suite under bun test, resolve any compatibility issues where appropriate, document any remaining limitations, and add a CI job to ensure Bun compatibility is continuously verified alongside the primary Vitest workflow.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mathew2k-hash to this issue.

[truthixify]

@Mathew2k-hash Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. Silence is the only thing that costs you the assignment; if you get stuck or context changes, just say so on the PR.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building.

[drips-wave]

Congratulations, @Mathew2k-hash! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Mathew2k-hash: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊