getsentry / getsentry/sentry-javascript

[Tracking Issue] Improve Bun Support

Open
#19,707 1 comment 3 reactions 0 assignees View on GitHub
Tracking Issue
Dominant language
TypeScript
Stars
8.7k
Forks
1.8k
Avg merge
1d 17h
Merged PRs (30d)
515

Description

The Bun runtime is [getting used more and more](https://www.npmcharts.com/compare/bun) and the JavaScript SDKs should support this ongoing trend. This issue is a tracking issue that shows current missing features with the Bun runtime.

### Missing auto-instrumentation (because `module.register` is not supported in Bun)

In general, a lot of missing auto-instrumentation is based on the missing support for `module.register` in Bun ([Bun docs](https://bun.com/docs/runtime/nodejs-compat#nodemodule)). Auto-instrumentation of ES Modules in OpenTelemetry is based on `import-in-the-middle` which calls `module.register`.

A real fix would require either (a) Bun improving `module.register()` + ESM namespace mutability support, or (b) the SDK implementing a Bun-specific loader (e.g., using Bun's native [plugin API](https://bun.com/docs/runtime/plugins)) to intercept imports before they are bound.

### Missing HTTP spans

The HTTP spans are created based on what diagnostic channels publish. Bun supports diagnostics channels but does not yet publish the necessary notifications. There is an open PR for that in Bun: https://github.com/oven-sh/bun/pull/24375

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.