Repository navigation
feat(nextjs): Use the Bun integrations when Next.js runs on Bun - #26294
Merged
JPeer264 merged 1 commit intoNov 13, 2026
Merged
Conversation
Contributor
size-limit report 📦Compared: d56b709 (PR test merge using develop at 93bc7af) Against: 621a801 (develop) · base run #65856
|
Contributor
Optional E2E testsSome optional checks were not successful. They do not block the merge. 4 not successful, 56 successful. See the run.
Successful checks
|
JPeer264
commented
Nov 11, 2026
| // Error should carry the parameterized transaction name | ||
| expect(errorEvent.transaction).toBe('GET /route-handler/[xoxo]/error'); | ||
| // `@sentry/nextjs` has no Deno entry, so Deno runs the Node.js entry. | ||
| expect(errorEvent.contexts?.runtime?.name).toBe(getRuntime() === 'deno' ? 'node' : getRuntime()); |
Member
Author
There was a problem hiding this comment.
This is getting removed in the next stack PR where Deno is being introduced
JPeer264
force-pushed
the
jp/nextjs-bun-entry
branch
from
November 11, 2026 15:09
ed8bd58 to
fc478d5
Compare
JPeer264
marked this pull request as ready for review
November 11, 2026 15:13
JPeer264
requested review from
chargome and
isaacs
and removed request for
msonnb
November 11, 2026 15:13
isaacs
force-pushed
the
jp/nextjs-bun-entry
branch
from
November 12, 2026 10:25
fc478d5 to
1f5e3a1
Compare
isaacs
force-pushed
the
jp/nextjs-bun-entry
branch
from
November 12, 2026 11:19
1f5e3a1 to
4999ca9
Compare
Adds a `bun` export condition. Its `init` replaces the undici fetch integration with the fetch integration of `@sentry/bun`, adds `bunHttpServerIntegration` to isolate requests, and reports Bun as the runtime. `@sentry/bun` is an optional peer dependency. Next.js bundles `@sentry/nextjs` without the `bun` condition, so `withSentryConfig` makes it external when the build runs on Bun. The Bun variant of the nextjs-16 e2e app now builds with `bun --bun next build` and does not add the Bun integrations by hand. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
force-pushed
the
jp/nextjs-bun-entry
branch
from
November 12, 2026 13:28
4999ca9 to
fda8b80
Compare
1 of 6 tasks
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
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.
part of #24830
part of JS-3835
This adds a
bunexport condition to@sentry/nextjs. On Bun,initadds the fetch integration andbunHttpServerIntegrationof@sentry/bunand reports Bun as the runtime. Whennext buildruns on Bun,withSentryConfigmakes@sentry/nextjsexternal, so Bun resolves it at run time and loads this entry.@sentry/bunis an optional peer dependency:Why
Without these integrations, all requests on Bun shared one trace and outgoing
fetchcalls had no spans, unless users added them by hand.CI decisions
The e2e jobs now use Bun 1.4.2, not 1.3.14. Bun 1.3 crashes in the Turbopack build when
applicationKeyis set. The alternative is a Bun version for each e2e variant.Known issues
@sentry/nextjs, so vinext apps on Bun must add it to therscexternals of Vite.@sentry/buninstalled, an app that loads the Bun entry fails at start.