Conversation
Contributor
size-limit report 📦
|
JPeer264
added this pull request to stack #24613
September 23, 2026 06:14
JPeer264
force-pushed
the
jp/node-suites-bun
branch
from
September 23, 2026 07:29
f544fac to
d5222d1
Compare
JPeer264
force-pushed
the
jp/node-suites-bun
branch
2 times, most recently
from
September 23, 2026 08:27
9099fef to
34ea3db
Compare
JPeer264
removed this pull request from stack #24613
September 23, 2026 09:51
JPeer264
added this pull request to stack #24633
September 23, 2026 09:51
JPeer264
force-pushed
the
jp/node-suites-bun
branch
from
September 23, 2026 10:02
34ea3db to
0a3ba84
Compare
The Bun package now selects every Node suite and excludes the ones that fail on Bun, grouped by cause: Node-only features, no `http.server` span because Bun does not publish `http.server.request.start`, no `fetch` instrumentation because Bun's `fetch` does not publish undici channels, no outgoing `node:http` instrumentation on Bun 1.3.14 (JS-3507), and no auto-instrumentation under `bun run` (JS-3508). Excluded files do not run, so the job stays fast. The list is based on Bun 1.3.14, the version CI pins. The Bun-only suites now use the shared Node runner instead of their own copy, so one runner serves all scenarios. The `captureMessage` test in `basic` is removed, because the shared `public-api` suites cover it with `@sentry/bun`, and `bun-runtime-metrics` runs on Bun instead of Node. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
force-pushed
the
jp/node-suites-bun
branch
from
September 23, 2026 10:04
0a3ba84 to
460db99
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bun now runs every Node suite except an explicit exclude list, grouped by cause, so a new Node test runs on Bun by default and a gap shows up as a failing test rather than as missing coverage. Excluded files do not run, which keeps the job fast even though most exclusions would otherwise wait for a timeout.
The exclude groups document what
@sentry/nodecurrently cannot do on Bun: nohttp.serverspan (Bun does not publishhttp.server.request.start), nofetchspans (Bun'sfetchdoes not use undici), no outgoingnode:httpinstrumentation on Bun 1.3.14 (JS-3507), and no auto-instrumentation underbun run(JS-3508). The list is based on Bun 1.3.14, the version CI pins; several suites already pass on newer Bun.The Bun-only suites now use the shared Node runner instead of their own copy of it.
Part of JS-3515.
🤖 Generated with Claude Code