test(nextjs): Add bun e2e test app by chargome · Pull Request #19318 · getsentry/sentry-javascript

chargome · 2026-02-13T10:49:39Z

Adds a new E2E test application (nextjs-16-bun) that runs Next.js 16 on Bun's runtime via bun --bun next build/start
Update CI to pick up this test for the bun runtime

Some limitations we ran into:

1. Outgoing fetch trace propagation is broken

sentry-trace and baggage headers are not attached to outgoing fetch() requests. The OTel nativeNodeFetchIntegration does not intercept Bun's native fetch implementation, so distributed tracing across services does not work. The inbound request starts a new trace instead of continuing the caller's trace.

2. HTTP request headers not extracted as span attributes

Inbound HTTP request headers (e.g. User-Agent, custom headers) are not populated as http.request.header.* attributes on server spans. The OTel HTTP instrumentation doesn't extract these when running on Bun.

Will create tickets for the findings.

ref https://linear.app/getsentry/issue/FE-713/investigate-nextjsbun-setup

linear · 2026-02-13T10:49:43Z

FE-713 Investigate Next.js+Bun setup

github-actions · 2026-02-13T10:58:30Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T11:00:32Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,101	-	9,125	-0%
GET With Sentry	1,684	19%	1,602	+5%
GET With Sentry (error only)	6,171	68%	5,883	+5%
POST Baseline	1,179	-	1,176	+0%
POST With Sentry	591	50%	561	+5%
POST With Sentry (error only)	1,015	86%	1,019	-0%
MYSQL Baseline	3,278	-	3,170	+3%
MYSQL With Sentry	469	14%	434	+8%
MYSQL With Sentry (error only)	2,677	82%	2,594	+3%

View base workflow run

s1gr1d · 2026-02-13T14:25:04Z

+import * as Sentry from '@sentry/nextjs';
+
+export async function register() {
+ if (process.env.NEXT_RUNTIME === 'nodejs') {


Q: is this still nodejs?

Still node yes

chargome · 2026-02-13T10:49:39Z

Adds a new E2E test application (nextjs-16-bun) that runs Next.js 16 on Bun's runtime via bun --bun next build/start
Update CI to pick up this test for the bun runtime

Some limitations we ran into:

1. Outgoing fetch trace propagation is broken

sentry-trace and baggage headers are not attached to outgoing fetch() requests. The OTel nativeNodeFetchIntegration does not intercept Bun's native fetch implementation, so distributed tracing across services does not work. The inbound request starts a new trace instead of continuing the caller's trace.

2. HTTP request headers not extracted as span attributes

Inbound HTTP request headers (e.g. User-Agent, custom headers) are not populated as http.request.header.* attributes on server spans. The OTel HTTP instrumentation doesn't extract these when running on Bun.

Will create tickets for the findings.

ref https://linear.app/getsentry/issue/FE-713/investigate-nextjsbun-setup

linear · 2026-02-13T10:49:43Z

FE-713 Investigate Next.js+Bun setup

github-actions · 2026-02-13T10:58:30Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T11:00:32Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,101	-	9,125	-0%
GET With Sentry	1,684	19%	1,602	+5%
GET With Sentry (error only)	6,171	68%	5,883	+5%
POST Baseline	1,179	-	1,176	+0%
POST With Sentry	591	50%	561	+5%
POST With Sentry (error only)	1,015	86%	1,019	-0%
MYSQL Baseline	3,278	-	3,170	+3%
MYSQL With Sentry	469	14%	434	+8%
MYSQL With Sentry (error only)	2,677	82%	2,594	+3%

View base workflow run

s1gr1d · 2026-02-13T14:25:04Z

+import * as Sentry from '@sentry/nextjs';
+
+export async function register() {
+ if (process.env.NEXT_RUNTIME === 'nodejs') {


Q: is this still nodejs?

Still node yes

chargome · 2026-02-13T10:49:39Z

Adds a new E2E test application (nextjs-16-bun) that runs Next.js 16 on Bun's runtime via bun --bun next build/start
Update CI to pick up this test for the bun runtime

Some limitations we ran into:

1. Outgoing fetch trace propagation is broken

sentry-trace and baggage headers are not attached to outgoing fetch() requests. The OTel nativeNodeFetchIntegration does not intercept Bun's native fetch implementation, so distributed tracing across services does not work. The inbound request starts a new trace instead of continuing the caller's trace.

2. HTTP request headers not extracted as span attributes

Inbound HTTP request headers (e.g. User-Agent, custom headers) are not populated as http.request.header.* attributes on server spans. The OTel HTTP instrumentation doesn't extract these when running on Bun.

Will create tickets for the findings.

ref https://linear.app/getsentry/issue/FE-713/investigate-nextjsbun-setup

linear · 2026-02-13T10:49:43Z

FE-713 Investigate Next.js+Bun setup

github-actions · 2026-02-13T10:58:30Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T11:00:32Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,101	-	9,125	-0%
GET With Sentry	1,684	19%	1,602	+5%
GET With Sentry (error only)	6,171	68%	5,883	+5%
POST Baseline	1,179	-	1,176	+0%
POST With Sentry	591	50%	561	+5%
POST With Sentry (error only)	1,015	86%	1,019	-0%
MYSQL Baseline	3,278	-	3,170	+3%
MYSQL With Sentry	469	14%	434	+8%
MYSQL With Sentry (error only)	2,677	82%	2,594	+3%

View base workflow run

s1gr1d · 2026-02-13T14:25:04Z

+import * as Sentry from '@sentry/nextjs';
+
+export async function register() {
+ if (process.env.NEXT_RUNTIME === 'nodejs') {


Q: is this still nodejs?

Still node yes

chargome · 2026-02-13T10:49:39Z

Adds a new E2E test application (nextjs-16-bun) that runs Next.js 16 on Bun's runtime via bun --bun next build/start
Update CI to pick up this test for the bun runtime

Some limitations we ran into:

1. Outgoing fetch trace propagation is broken

sentry-trace and baggage headers are not attached to outgoing fetch() requests. The OTel nativeNodeFetchIntegration does not intercept Bun's native fetch implementation, so distributed tracing across services does not work. The inbound request starts a new trace instead of continuing the caller's trace.

2. HTTP request headers not extracted as span attributes

Inbound HTTP request headers (e.g. User-Agent, custom headers) are not populated as http.request.header.* attributes on server spans. The OTel HTTP instrumentation doesn't extract these when running on Bun.

Will create tickets for the findings.

ref https://linear.app/getsentry/issue/FE-713/investigate-nextjsbun-setup

linear · 2026-02-13T10:49:43Z

FE-713 Investigate Next.js+Bun setup

github-actions · 2026-02-13T10:58:30Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T11:00:32Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,101	-	9,125	-0%
GET With Sentry	1,684	19%	1,602	+5%
GET With Sentry (error only)	6,171	68%	5,883	+5%
POST Baseline	1,179	-	1,176	+0%
POST With Sentry	591	50%	561	+5%
POST With Sentry (error only)	1,015	86%	1,019	-0%
MYSQL Baseline	3,278	-	3,170	+3%
MYSQL With Sentry	469	14%	434	+8%
MYSQL With Sentry (error only)	2,677	82%	2,594	+3%

View base workflow run

s1gr1d · 2026-02-13T14:25:04Z

+import * as Sentry from '@sentry/nextjs';
+
+export async function register() {
+ if (process.env.NEXT_RUNTIME === 'nodejs') {


Q: is this still nodejs?

Still node yes

chargome · 2026-02-13T10:49:39Z

Adds a new E2E test application (nextjs-16-bun) that runs Next.js 16 on Bun's runtime via bun --bun next build/start
Update CI to pick up this test for the bun runtime

Some limitations we ran into:

1. Outgoing fetch trace propagation is broken

sentry-trace and baggage headers are not attached to outgoing fetch() requests. The OTel nativeNodeFetchIntegration does not intercept Bun's native fetch implementation, so distributed tracing across services does not work. The inbound request starts a new trace instead of continuing the caller's trace.

2. HTTP request headers not extracted as span attributes

Inbound HTTP request headers (e.g. User-Agent, custom headers) are not populated as http.request.header.* attributes on server spans. The OTel HTTP instrumentation doesn't extract these when running on Bun.

Will create tickets for the findings.

ref https://linear.app/getsentry/issue/FE-713/investigate-nextjsbun-setup

linear · 2026-02-13T10:49:43Z

FE-713 Investigate Next.js+Bun setup

github-actions · 2026-02-13T10:58:30Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T11:00:32Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,101	-	9,125	-0%
GET With Sentry	1,684	19%	1,602	+5%
GET With Sentry (error only)	6,171	68%	5,883	+5%
POST Baseline	1,179	-	1,176	+0%
POST With Sentry	591	50%	561	+5%
POST With Sentry (error only)	1,015	86%	1,019	-0%
MYSQL Baseline	3,278	-	3,170	+3%
MYSQL With Sentry	469	14%	434	+8%
MYSQL With Sentry (error only)	2,677	82%	2,594	+3%

View base workflow run

s1gr1d · 2026-02-13T14:25:04Z

+import * as Sentry from '@sentry/nextjs';
+
+export async function register() {
+ if (process.env.NEXT_RUNTIME === 'nodejs') {


Q: is this still nodejs?

Still node yes

chargome · 2026-02-13T10:49:39Z

Adds a new E2E test application (nextjs-16-bun) that runs Next.js 16 on Bun's runtime via bun --bun next build/start
Update CI to pick up this test for the bun runtime

Some limitations we ran into:

1. Outgoing fetch trace propagation is broken

sentry-trace and baggage headers are not attached to outgoing fetch() requests. The OTel nativeNodeFetchIntegration does not intercept Bun's native fetch implementation, so distributed tracing across services does not work. The inbound request starts a new trace instead of continuing the caller's trace.

2. HTTP request headers not extracted as span attributes

Inbound HTTP request headers (e.g. User-Agent, custom headers) are not populated as http.request.header.* attributes on server spans. The OTel HTTP instrumentation doesn't extract these when running on Bun.

Will create tickets for the findings.

ref https://linear.app/getsentry/issue/FE-713/investigate-nextjsbun-setup

linear · 2026-02-13T10:49:43Z

FE-713 Investigate Next.js+Bun setup

github-actions · 2026-02-13T10:58:30Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T11:00:32Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,101	-	9,125	-0%
GET With Sentry	1,684	19%	1,602	+5%
GET With Sentry (error only)	6,171	68%	5,883	+5%
POST Baseline	1,179	-	1,176	+0%
POST With Sentry	591	50%	561	+5%
POST With Sentry (error only)	1,015	86%	1,019	-0%
MYSQL Baseline	3,278	-	3,170	+3%
MYSQL With Sentry	469	14%	434	+8%
MYSQL With Sentry (error only)	2,677	82%	2,594	+3%

View base workflow run

s1gr1d · 2026-02-13T14:25:04Z

+import * as Sentry from '@sentry/nextjs';
+
+export async function register() {
+ if (process.env.NEXT_RUNTIME === 'nodejs') {


Q: is this still nodejs?

Still node yes

chargome · 2026-02-13T10:49:39Z

Adds a new E2E test application (nextjs-16-bun) that runs Next.js 16 on Bun's runtime via bun --bun next build/start
Update CI to pick up this test for the bun runtime

Some limitations we ran into:

1. Outgoing fetch trace propagation is broken

sentry-trace and baggage headers are not attached to outgoing fetch() requests. The OTel nativeNodeFetchIntegration does not intercept Bun's native fetch implementation, so distributed tracing across services does not work. The inbound request starts a new trace instead of continuing the caller's trace.

2. HTTP request headers not extracted as span attributes

Inbound HTTP request headers (e.g. User-Agent, custom headers) are not populated as http.request.header.* attributes on server spans. The OTel HTTP instrumentation doesn't extract these when running on Bun.

Will create tickets for the findings.

ref https://linear.app/getsentry/issue/FE-713/investigate-nextjsbun-setup

linear · 2026-02-13T10:49:43Z

FE-713 Investigate Next.js+Bun setup

github-actions · 2026-02-13T10:58:30Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T11:00:32Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,101	-	9,125	-0%
GET With Sentry	1,684	19%	1,602	+5%
GET With Sentry (error only)	6,171	68%	5,883	+5%
POST Baseline	1,179	-	1,176	+0%
POST With Sentry	591	50%	561	+5%
POST With Sentry (error only)	1,015	86%	1,019	-0%
MYSQL Baseline	3,278	-	3,170	+3%
MYSQL With Sentry	469	14%	434	+8%
MYSQL With Sentry (error only)	2,677	82%	2,594	+3%

View base workflow run

s1gr1d · 2026-02-13T14:25:04Z

+import * as Sentry from '@sentry/nextjs';
+
+export async function register() {
+ if (process.env.NEXT_RUNTIME === 'nodejs') {


Q: is this still nodejs?

Still node yes

chargome · 2026-02-13T10:49:39Z

Adds a new E2E test application (nextjs-16-bun) that runs Next.js 16 on Bun's runtime via bun --bun next build/start
Update CI to pick up this test for the bun runtime

Some limitations we ran into:

1. Outgoing fetch trace propagation is broken

sentry-trace and baggage headers are not attached to outgoing fetch() requests. The OTel nativeNodeFetchIntegration does not intercept Bun's native fetch implementation, so distributed tracing across services does not work. The inbound request starts a new trace instead of continuing the caller's trace.

2. HTTP request headers not extracted as span attributes

Inbound HTTP request headers (e.g. User-Agent, custom headers) are not populated as http.request.header.* attributes on server spans. The OTel HTTP instrumentation doesn't extract these when running on Bun.

Will create tickets for the findings.

ref https://linear.app/getsentry/issue/FE-713/investigate-nextjsbun-setup

linear · 2026-02-13T10:49:43Z

FE-713 Investigate Next.js+Bun setup

github-actions · 2026-02-13T10:58:30Z

Codecov Results 📊

Generated by Codecov Action

github-actions · 2026-02-13T11:00:32Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,101	-	9,125	-0%
GET With Sentry	1,684	19%	1,602	+5%
GET With Sentry (error only)	6,171	68%	5,883	+5%
POST Baseline	1,179	-	1,176	+0%
POST With Sentry	591	50%	561	+5%
POST With Sentry (error only)	1,015	86%	1,019	-0%
MYSQL Baseline	3,278	-	3,170	+3%
MYSQL With Sentry	469	14%	434	+8%
MYSQL With Sentry (error only)	2,677	82%	2,594	+3%

View base workflow run

s1gr1d · 2026-02-13T14:25:04Z

+import * as Sentry from '@sentry/nextjs';
+
+export async function register() {
+ if (process.env.NEXT_RUNTIME === 'nodejs') {


Q: is this still nodejs?

Still node yes

add bun e2e test for nextjs
cd88597

chargome self-assigned this Feb 13, 2026

chargome changed the title ~~text(nextjs): Add bun e2e test app~~test(nextjs): Add bun e2e test appFeb 13, 2026

format
f5aff65

chargome requested review from isaacs and logaretm February 13, 2026 11:32

chargome enabled auto-merge (squash) February 13, 2026 12:52

chargome requested a review from s1gr1d February 13, 2026 12:55

s1gr1d approved these changes Feb 13, 2026
View reviewed changes

chargome merged commit fb52cd2 into developFeb 13, 2026
70 checks passed

chargome deleted the cg-next-bun-e2e branch February 13, 2026 14:25

logaretm mentioned this pull request Feb 20, 2026
meta(changelog): Update changelog for 10.40.0 #19459
Closed

This was referenced Feb 24, 2026
Update dependency @sentry/browser to v10.40.0 danielemery/quizlord-client#304
Merged
Update sentry-javascript monorepo to v10.40.0 danielemery/quizlord-api#419
Merged

github-actionsBot mentioned this pull request Feb 24, 2026
chore(deps): update JavaScript SDK to v10.40.0 getsentry/sentry-react-native#5715
Merged

have-renovateBot mentioned this pull request Feb 24, 2026
chore(deps): update @sentry/node to v10 happyvertical/sdk#827
Merged
1 task

This was referenced Feb 24, 2026
Update sentry-javascript monorepo from v7.120.4 to v10 entur/udug#423
Open
fix(deps): update dependency @sentry/react to v10 graasp/graasp-app-multiple-choice-question#258
Open
⬆️ Upgrade sentry-javascript monorepo to v10 captive-studio/es-packages#1537
Open

konflux-stagingBot mentioned this pull request Mar 10, 2026
chore(deps): update dependency @sentry/react to v10.43.0 testcara/konflux-ui#124
Open
1 task

This was referenced Mar 10, 2026
Update dependency @sentry/browser to v10.40.0 naymspace/backpex#1863
Merged
chore(deps): update dependency @sentry/react to v10.43.0 giantswarm/backstage#1361
Merged

github-actionsBot mentioned this pull request Mar 11, 2026
chore(deps): update JavaScript SDK to v10.49.0 glemartret/sentry-dart#1
Open

This was referenced Mar 21, 2026
Update dependency @sentry/node to v10 sderickson/saflib#230
Merged
chore(deps): update dependency @sentry/nextjs to v10.46.0 m1m0zzz/visualizers#16
Merged
chore(deps): update all non-major dependencies MooncellWiki/prts-widgets#286
Merged

red-hat-konfluxBot mentioned this pull request Mar 24, 2026
fix(deps): update dependency @sentry/browser to v10 RedHatInsights/uhc-portal#413
Closed
1 task

konflux-stagingBot mentioned this pull request Apr 1, 2026
chore(deps): update dependency @sentry/react to v10.50.0 testcara/konflux-ui-test#53
Open
1 task

renovateBot mentioned this pull request Apr 2, 2026
fix(deps): update dependency @sentry/sveltekit to ^10.45.0 Seenivers/App#612
Merged
1 task