bun default integrations diverge from Node's

Open Beginner friendly
#23,887 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
observability-sre

Research direction

Compare packages/bun/src/sdk.ts:48 with node/src/sdk/index.ts:getBaseDefaultIntegrations, then review the integration definitions for conversationIdIntegration and systemErrorIntegration. Add the conversation integration, decide the system-error behavior, and document the intentional child-process and worker-thread omissions with a reference to issue #20237; done means Bun's defaults and comments reflect these decisions.

Written by the indexing model from the issue text.

Description

Bun Feature javascript

packages/bun/src/sdk.ts:48 omits, relative to node/src/sdk/index.ts:getBaseDefaultIntegrations:

Integration Note
conversationIdIntegration pure core JS, no Node API. Cloudflare and vercel-edge both include it. Without it, setConversationId has no effect on gen_ai.* spans under Bun.
systemErrorIntegration needs a check
childProcessIntegration relies on child_process diagnostics channels Bun does not emit (see B1), so probably correct to omit, but say so in a comment
workerThreadsIntegration same

Work item. Add conversationIdIntegration() to Bun's defaults. For each remaining omission, either add it or leave a one-line comment saying which Bun gap makes it a no-op.

**Prior art **(tracked). #20237 (closed, not planned) already settled the childProcessIntegration and workerThreadsIntegration question, and documents the same root cause as B1: Bun implements the node:diagnostics_channel API but never publishes to the child_process or worker_threads channels. Omitting those two is correct; cite that issue in the comment. Nothing covers conversationIdIntegration or systemErrorIntegration on Bun.

Dominant language
TypeScript
Stars
8.7k
Forks
1.9k
Avg merge
1d 17h
Merged PRs (30d)
521

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-javascript

All issues in getsentry/sentry-javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.