Skip to content

chore(bun): Fix stale comment in getPerformanceIntegrations #24533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JPeer264 merged 1 commit into from
Sep 21, 2026
+3 −6
Merged

chore(bun): Fix stale comment in getPerformanceIntegrations #24533

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions packages/bun/src/sdk.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,12 +28,9 @@ import { bunHttpServerIntegration } from './integrations/bunHttpServer';
import { getErrorIntegrations, getTracingIntegrations } from '@sentry/server-utils';

/**
* The performance integrations for bun: the OTel auto-performance set, but with
* the orchestrion diagnostics-channel subscribers swapped in for their OTel
* equivalents *only* when the orchestrion channels were actually injected (i.e.
* the app was built with `@sentry/bun/plugin`). Without that, the channels
* never fire — and the OTel versions rely on a runtime require-hook bun doesn't
* support — so leave the auto-performance set alone.
* The tracing integrations for bun, added whenever spans are enabled. Most of them listen on
* the orchestrion diagnostics channels, which only exist when the app is built with
* `@sentry/bun/plugin`. Without the plugin, those integrations stay installed but create no spans.
*/
function getPerformanceIntegrations(options: Options): Integration[] {
if (!hasSpansEnabled(options)) {
Expand Down
Loading