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-build
branch
2 times, most recently
from
September 23, 2026 08:11
99acd71 to
5eb22a2
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
2 times, most recently
from
September 23, 2026 09:49
48d16a8 to
51be7dc
Compare
JPeer264
removed this pull request from stack #24613
September 23, 2026 09:51
JPeer264
changed the base branch from
jp/node-suites-deno
to
jp/node-suites-bun-sdk-fixes
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-build
branch
2 times, most recently
from
September 23, 2026 10:02
9fc4460 to
131b223
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
from
September 23, 2026 10:04
131b223 to
6c3bef1
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
2 times, most recently
from
September 23, 2026 12:24
686046a to
b0517c0
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
2 times, most recently
from
September 23, 2026 13:31
f58de0f to
b8c9dc6
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
from
September 23, 2026 16:19
b8c9dc6 to
f25eee7
Compare
JPeer264
removed this pull request from stack #24633
September 23, 2026 16:19
JPeer264
added this pull request to stack #24670
September 23, 2026 16:19
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
from
September 23, 2026 16:40
f25eee7 to
4739836
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
2 times, most recently
from
September 23, 2026 16:59
71f4ecd to
c7d69ba
Compare
JPeer264
removed this pull request from stack #24670
September 23, 2026 17:26
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
from
September 23, 2026 17:27
c7d69ba to
1a809bc
Compare
JPeer264
added this pull request to stack #24671
September 23, 2026 17:31
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
from
September 24, 2026 09:13
1a809bc to
134861e
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
from
September 24, 2026 09:24
134861e to
f0036b9
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
2 times, most recently
from
September 24, 2026 14:19
8baec53 to
c37936a
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
from
September 25, 2026 10:53
c37936a to
51538c3
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
3 times, most recently
from
September 25, 2026 15:49
dbd8717 to
b6e2d06
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
3 times, most recently
from
September 27, 2026 14:03
b2d85de to
bab2eac
Compare
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
from
September 27, 2026 14:57
bab2eac to
f7bb4f9
Compare
JPeer264
added a commit
that referenced
this pull request
Sep 27, 2026
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/node` currently cannot do on Bun: no `http.server` span (Bun does not publish `http.server.request.start`), no `fetch` spans (Bun's `fetch` does not use undici), no outgoing `node:http` instrumentation on Bun 1.3.14 (#23881), and no auto-instrumentation under `bun run` (#23882). The list is based on Bun 1.3.14, the version CI pins; several suites already pass on newer Bun. The suites that assert the SDK name use `EXPECTED_SDK_NAME`, so they also pass in the `@sentry/bun` project. FWIW in a later PR more tests will be enabled as Bun will then run `Bun.build` before - see #24612 Part of #23889. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: isaacs <i@izs.me>
Under `bun run` the SDK cannot inject the diagnostics channels into
libraries (JS-3508), so Bun apps must be built with `@sentry/bun/plugin`
to get framework, database and AI spans. The new `node-suites-bun-build`
project tests that path: the runner builds each scenario with the plugin
right before it starts (`RUNTIME_BUILD_SCRIPT`), and runs the bundle
with `@sentry/bun`.
The Docker suites run as well, so the Bun CI job gets the disk space
step of the Node and Deno jobs. `pg-native` and the CommonJS
`postgresjs` tests are skipped on Bun: the `libpq` addon needs a Node
symbol that Bun does not have, and through the `bun` export condition
`require('postgres')` returns the ES module namespace.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
force-pushed
the
jp/node-suites-bun-build
branch
from
September 27, 2026 15:54
f7bb4f9 to
f5caf00
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.
Under
bun runthe SDK cannot inject diagnostics channels into libraries (#23882), so a Bun app only gets framework, database and AI spans when it is built with@sentry/bun/plugin. That path had no integration coverage. The newnode-suites-bun-buildproject bundles each auto-instrumentation scenario with the plugin right before it starts and runs it with@sentry/bun. Express, Fastify, Hapi, Koa, Apollo, most AI suites and the Docker database suites now run on Bun.pg-nativeand the CommonJSpostgresjstests are skipped on Bun: thelibpqaddon needs a Node symbol that Bun does not have, and through thebunexport conditionrequire('postgres')returns the ES module namespace.Closes #23889.
🤖 Generated with Claude Code