@sentry/gatsby

Important Changes

• Add a managed tunnel that the SDK derives from the DSN (#25199, #25200, #25783)

  Set tunnel: true in your browser Sentry.init call to send events through your own server. This helps when ad blockers block requests to Sentry. The browser derives the tunnel path from the DSN, so older and newer builds of your client and server always agree on the path.

  To serve the tunnel, add serveTunnelIntegration() to your server SDK. Astro, Nuxt, Nitro, React Router, Remix 3, SolidStart, SvelteKit and TanStack Start then answer tunnel requests automatically:

  // browser
  Sentry.init({ dsn, tunnel: true });
  
  // server
  Sentry.init({ dsn, integrations: [Sentry.serveTunnelIntegration()] });

  If the browser uses a different DSN than the server, set serveTunnelIntegration({ allowedDsns: [browserDsn] }). For other setups, the server SDKs export handleTunnelRequestIfMatched, handleTunnelRequest, isTunnelRequest and getTunnelPath:

  app.use((req, res, next) => Sentry.handleTunnelRequestIfMatched(req, res) ?? next());

  The request option of handleTunnelRequest is deprecated and will be removed in v12.

• Make span origins spec compliant

  Some span origins changed their names to follow the trace origin spec:

  • auto.amqplib.* is now auto.queue.amqplib.*, and auto.kafkajs.* is now auto.queue.kafkajs.*.

  • auto.vercelai.channel is now auto.ai.vercelai.

  • auto.firebase.firestore is now auto.db.firebase.firestore, and auto.firebase.functions is now auto.function.firebase.

  • auto.aws.aws_sdk is now auto.{rpc,db,queue,ai}.aws_sdk, with the category from the span op.

  • auto.aws_lambda is now auto.function.aws_serverless.

  • auto.mcp.notification is now auto.function.mcp_server.notification.

  • auto.db.cloudflare.durable_object.sql is now auto.db.cloudflare.durable_object_sql.

  • auto.http.browser.{lcp,cls,inp} is now auto.ui.browser.{lcp,cls,inp}.

  If you have ignoreSpans rules, queries or alerts on the old origins, change them to use the new origins.

• bun: Add incoming request options and request sessions to bunServerIntegration

  bunServerIntegration now accepts the same options as denoServeIntegration: ignoreRequestBody, ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated, onSpanEnd, sessions and sessionFlushingDelayMS. The callbacks receive the web Request.

  Bun.serve now records a request session for each incoming request. Sessions are sent only when a release is set. To turn them off, set bunServerIntegration({ sessions: false }).

  ignoreStaticAssets defaults to true, so Bun.serve no longer creates spans for GET requests to common static assets such as favicon.ico, robots.txt or *.js files. To keep these spans, set bunServerIntegration({ ignoreStaticAssets: false }). Bun.serve spans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown for OPTIONS and HEAD requests are now captured.

• bun: Inject debug IDs and upload source maps in sentryBunPlugin

  sentryBunPlugin from @sentry/bun/plugin now accepts the same options as sentryEsbuildPlugin (org, project, authToken, release, sourcemaps, ...). When Bun.build writes source maps to outdir, the plugin injects the debug ID that Bun writes into each bundle, injects the release, and uploads the source maps at the end of the build. You no longer need to run sentry sourcemap inject and sentry sourcemap upload after the build.

  Like the other bundler plugins, sentryBunPlugin now sends build telemetry and injects the release it detects (for example, from git). To turn off telemetry, set telemetry: false.

• cloudflare: Add incoming request span options to httpServerIntegration

  Cloudflare's httpServerIntegration now accepts ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated and onSpanEnd, with the same meaning as in the Node, Deno and Bun integrations. The callbacks receive the web Request.

  ignoreStaticAssets defaults to true, so workers no longer create spans for GET requests to common static assets such as favicon.ico, robots.txt or *.js files. To keep these spans, set httpServerIntegration({ ignoreStaticAssets: false }). Request spans also follow the client's tracing configuration by default, so the SDK does not start them when tracing is disabled. If ignoreRequestBody throws, the request no longer fails, and the SDK skips the body.

• cloudflare: Let users configure the channel integrations

  When the @sentry/cloudflare/vite plugin bundles an instrumented package (for example pg or openai), the SDK adds the matching integration with its default options. @sentry/cloudflare now exports these integrations, so you can set their options, for example in instrument.server.ts:

  export default Sentry.defineCloudflareOptions(env => ({
    dsn: env.SENTRY_DSN,
    integrations: [Sentry.openAIIntegration({ recordInputs: false, recordOutputs: false })],
  }));

  These integrations need the vite plugin. Without it, they record nothing, and with debug: true the SDK logs a warning.

• node: Add onSpanEnd to httpIntegration

  httpIntegration and httpServerSpansIntegration now accept onSpanEnd, a hook that runs when the response for an incoming request finishes, before its span ends. Use it to change the span based on the response. Deno and Bun already have this option.

• node, bun, deno, cloudflare: Align portable exports across server SDKs

  Node, Bun, Deno and Cloudflare now export the same helpers from @sentry/core and @sentry/server-utils where they work on that runtime:

  • Node and Bun now export moduleMetadataIntegration, instrumentPostgresJsSql, instrumentCreateReactAgent, awsIntegration and the FlueOptions type. awsIntegration was already in their default integrations.

  • Deno and Cloudflare now export parameterize and instrumentStateGraphCompile.

  • Bun and Cloudflare now export the Log and LogSeverityLevel types.

  • Deno now exports fastifyIntegration, which was already in its default integrations.

• nuxt: Start the server SDK on the Nuxt Vite server (experimental)

  Sentry now supports Node.js production builds using Nuxt 4.6's experimental Vite server (server: { builder: 'vite' }). Your sentry.server.config loads automatically, enabling request tracing and automatic database spans for supported libraries.

  Development mode, Cloudflare, automatic capture of server rendering errors, and connecting server and browser traces via HTML meta tags are not yet supported. This experimental support may change in minor releases.

Other Changes

• Export the Node bundler plugins from SDKs that wrap @sentry/node

• cloudflare: Instrument Workers KV bindings

• nextjs: Warn when Next.js production builds miss the instrumentation file

• react-router: Support renderToReadableStream in createSentryHandleRequest

• server-utils: Emit execute_tool spans for Anthropic's beta.sessions.events.toolRunner()

• server-utils: Record Workers AI Clairic calls as gen_ai.extract spans

• server-utils: Instrument together-ai 1.x

• browser: Preserve empty stacks in continuous profiles

• browser: Resolve request URLs against location.href in tracing

• build: Make CJS re-exports visible to Node ESM imports

• bun: Add systemErrorIntegration to default integrations

• cloudflare: Bind a default re-export with var in the Vite transform

• cloudflare: Do not add back channel integrations the user removed

• cloudflare: Skip comments when locating the default keyword in the Vite transform

• core: Allow project arrays in framework build options

• core: Drop sampled-out errors before they take a promise buffer slot

• core: End node:http client spans when the response is destroyed

• core: Preserve AI proxy property references

• core: Resolve relative URLs when enhancing fetch error messages

• feedback: Wait for frames without the form before capturing the screenshot

• hono: Make the Hono middleware types compile on Hono 5

• node: Flush buffered streamed spans on process exit

• node: Read module versions from the isolated layouts of pnpm and Bun

• node: Set the eve conversation id on model.started for eve 0.84+

• node: Skip spans for outgoing requests to Sentry via undici fetch and node:http

• node: Use the request method for Hapi routes with multiple methods

• nuxt,nitro: Accept Nitro 3 betas without narrowing peer support

• opentelemetry: Convert OpenTelemetry performance.now() timestamps

• react: Avoid double slashes in manifest route names

• react: Parameterize React Router transactions with encoded params

• remix: Drop Remix 3 release candidates from the peer range

• replay: Apply attribute masking to breadcrumb messages

• server-utils: Cap the runs the LangChain callback handler keeps open

• server-utils: Keep OpenAI streamed tool calls that have no index

• server-utils: Keep OpenRouter evaluation confidence and legend on Vercel AI spans

• server-utils: Nest Flue runs on Node under the request that dispatched them

• server-utils: Record AI SDK tool spans for tools run outside its tool loop

• server-utils: Use cumulative input and cache token counts from streamed message_delta

• server-utils: Use the stored pi-durable session id as conversation id

• tanstackstart-react: Unminify server errors in Nitro builds

Internal Changes

• Remove permissions from settings.json

Work in this release was contributed by @4ktLuffy, @faizansaiyed123, @itisrmk, @kunal649, @kyrylolvov, @larcane97, @lfantone, @pcbeingused333, @psh4607, and @seongwon030. Thank you for your contributions!

Bundle size