| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
size-limit report 📦
|
Sorry, something went wrong.
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>
| Back | FazBrowse Home | New Git URL |
Under bun run the 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 new node-suites-bun-build project 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-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.
Closes #23889.
🤖 Generated with Claude Code