getsentry / getsentry/sentry-javascript

[Tracking Issue] Improve Bun Support

Offen
#19,707 1 Kommentar 3 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Tracking Issue
Vorherrschende Sprache
TypeScript
Sterne
8.7k
Forks
1.8k
Ø Merge
1 T. 17 Std.
Gemergte PRs (30 T.)
515

Beschreibung

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

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.