feat: Accept `tunnel: true` in `init` to enable the managed tunnel by logaretm · Pull Request #25200 · getsentry/sentry-javascript

feat: Accept `tunnel: true` in `init` to enable the managed tunnel

logaretm

committed

7cc3b00

feat: Explain a managed tunnel that nothing on the server answers

logaretm

committed

4911924

fix(core): Keep the managed tunnel warning out of production bundles

logaretm

committed

d138861

fix(aws-serverless): Keep the managed tunnel when the Lambda extension sends events

logaretm

committed

f651a97

fix(core): Point Next.js users to `tunnelRoute` when the managed tunnel isn't served

logaretm

committed

36c4a1a

feat(browser): Send directly to Sentry when nothing answers the managed tunnel

logaretm

committed

5d4afe9

fix(browser): Normalize the managed tunnel's base path like the server does

logaretm

committed

5ebb8e9

fix(browser): Keep the managed tunnel when Sentry answers 404 or 405 through it

logaretm

committed

1f23d5a

fix(browser): Send directly when anything but the tunnel answers a managed tunnel request with a 4xx

logaretm

committed

36dfaab

ref(browser): Warn about a rejected DSN from the managed tunnel transport, and import server helpers from core/server

logaretm

committed

f0b532c

ref(browser): Switch the managed tunnel to direct sends in one place

logaretm

committed

6f1d9c9

test(browser): Drop the server-side tunnel match from the browser tunnel tests

logaretm

committed

e6ff11a

ref(browser): Trim the managed tunnel comments

logaretm

committed

695feb9

fix(aws-serverless): Keep the Lambda extension for a relative tunnel path, which is the managed tunnel to serve

logaretm

committed

a90bd51

ref: Import the internal tunnel helpers under their `_INTERNAL_` names

logaretm

committed

8d266b5

ref: Narrow `tunnel` to the browser or server tunnel options per SDK

logaretm

committed

a80ac61

feat(browser): Treat a relative tunnel path as a managed one and only fall back on 404 or 405

logaretm

committed

ba73fb1

ref(browser): Fold the managed tunnel fallback into the fetch transport

logaretm

committed

ee14703

fix(browser): Resend to Sentry after the tunnel request leaves the keepalive totals

logaretm

committed

9f5229d

Navigation Menu

Repository navigation

feat: Accept `tunnel: true` in `init` to enable the managed tunnel - #25200

feat: Accept `tunnel: true` in `init` to enable the managed tunnel#25200
logaretm wants to merge 19 commits into
developfrom
awad/tunnel-browser-managed

Commits on Oct 23, 2026

feat: Accept `tunnel: true` in `init` to enable the managed tunnel

feat: Explain a managed tunnel that nothing on the server answers

fix(core): Keep the managed tunnel warning out of production bundles

fix(aws-serverless): Keep the managed tunnel when the Lambda extension sends events

fix(core): Point Next.js users to `tunnelRoute` when the managed tunnel isn't served

feat(browser): Send directly to Sentry when nothing answers the managed tunnel

fix(browser): Normalize the managed tunnel's base path like the server does

fix(browser): Keep the managed tunnel when Sentry answers 404 or 405 through it

fix(browser): Send directly when anything but the tunnel answers a managed tunnel request with a 4xx

ref(browser): Warn about a rejected DSN from the managed tunnel transport, and import server helpers from core/server

ref(browser): Switch the managed tunnel to direct sends in one place

test(browser): Drop the server-side tunnel match from the browser tunnel tests

ref(browser): Trim the managed tunnel comments

fix(aws-serverless): Keep the Lambda extension for a relative tunnel path, which is the managed tunnel to serve

ref: Import the internal tunnel helpers under their `_INTERNAL_` names

ref: Narrow `tunnel` to the browser or server tunnel options per SDK

feat(browser): Treat a relative tunnel path as a managed one and only fall back on 404 or 405

ref(browser): Fold the managed tunnel fallback into the fetch transport

fix(browser): Resend to Sentry after the tunnel request leaves the keepalive totals