@sentry/node

• deprecated

  replay/v9: Deprecate _experiments.autoFlushOnFeedback

• v9/core: Add shared flushIfServerless function

• v9/react-router: Add createSentryHandleError

• v9/react-router: Automatically flush on serverless for loaders/actions

• v9/react-router: Automatically flush on serverless for request handler

• v9/astro: Construct parametrized route during runtime

• v9/nextjs: Flush in route handlers

• v9/node: Fix exports for openai instrumentation

• v9/core: Add MCP server instrumentation

• v9/meta: Unify detection of serverless environments and add Cloud Run

• v9/node: Add mechanism to fastifyIntegration error handler

• v9/replay: Fix re-sampled sessions after a click

• v9/aws: Detect SDK source for AWS Lambda layer

• v9/core: Fix OpenAI SDK private field access by binding non-instrumented fns

• v9/core: Update ai.response.object to gen_ai.response.object

• v9/nextjs: Update stackframe calls for next v15.5

Important Changes

• deprecated

  v9/core: Deprecate experimental enableLogs and beforeSendLog option

Sentry now has support for structured logging. Previously to enable structured logging, you had to use the _experiments.enableLogs and _experiments.beforeSendLog options. These options have been deprecated in favor of the top-level enableLogs and beforeSendLog options.

// before
Sentry.init({
  _experiments: {
    enableLogs: true,
    beforeSendLog: log => {
      return log;
    },
  },
});

// after
Sentry.init({
  enableLogs: true,
  beforeSendLog: log => {
    return log;
  },
});

• astro: Implement parameterized routes

  • feat(v9/astro): Parametrize dynamic server routes

  • feat(v9/astro): Parametrize routes on client-side

Server-side and client-side parameterized routes are now supported in the Astro SDK. No configuration changes are required.

Other Changes

• v9/node: Add shouldHandleError option to fastifyIntegration

• fix(v9/cloudflare) Allow non UUID workflow instance IDs

• v9/node: Ensure tool errors for vercelAiIntegration have correct trace

• v9/remix: Ensure source maps upload fails silently if Sentry CLI fails

• v9/svelte: Do not insert preprocess code in script module in Svelte 5

Work in this release was contributed by @richardjelinek-fastest. Thank you for your contribution!

Important Changes

• browser: Add debugId sync APIs between web worker and main thread

This release adds two Browser SDK APIs to let the main thread know about debugIds of worker files:

• webWorkerIntegration({worker}) to be used in the main thread

• registerWebWorker({self}) to be used in the web worker

// main.js
Sentry.init({...})

const worker = new MyWorker(...);

Sentry.addIntegration(Sentry.webWorkerIntegration({ worker }));

worker.addEventListener('message', e => {...});

// worker.js
Sentry.registerWebWorker({ self });

self.postMessage(...);

• deprecated

  core: Deprecate logger in favor of debug

The internal SDK logger export from @sentry/core has been deprecated in favor of the debug export. debug only exposes log, warn, and error methods but is otherwise identical to logger. Note that this deprecation does not affect the logger export from other packages (like @sentry/browser or @sentry/node) which is used for Sentry Logging.

import { logger, debug } from '@sentry/core';

// before
logger.info('This is an info message');

// after
debug.log('This is an info message');

• node: Add OpenAI integration

This release adds official support for instrumenting OpenAI SDK calls in with Sentry tracing, following OpenTelemetry semantic conventions for Generative AI. It instruments:

• client.chat.completions.create() - For chat-based completions

• client.responses.create() - For the responses API

// The integration respects your `sendDefaultPii` option, but you can override the behavior in the integration options

Sentry.init({
  dsn: '__DSN__',
  integrations: [
    Sentry.openAIIntegration({
      recordInputs: true, // Force recording prompts
      recordOutputs: true, // Force recording responses
    }),
  ],
});

Other Changes

• node-core: Expand @opentelemetry/instrumentation range to cover 0.203.0

• cloudflare: Ensure errors get captured from durable objects

• sveltekit: Ensure server errors from streamed responses are sent

Work in this release was contributed by @0xbad0c0d3 and @tommy-gilligan. Thank you for your contributions!

Important Changes

• browser: Add afterStartPageloadSpan hook to improve spanId assignment on web vital spans

This PR adds a new afterStartPageloadSpan lifecycle hook to more robustly assign the correct pageload span ID to web vital spans, replacing the previous unreliable "wait for a tick" approach with a direct callback that fires when the pageload span becomes available.

• nextjs: Client-side parameterized routes

This PR implements client-side parameterized routes for Next.js by leveraging an injected manifest within the existing app-router instrumentation to automatically parameterize all client-side transactions (e.g. users/123 and users/456 now become become users/:id).

• node: Drop 401-404 and 3xx status code spans by default

This PR changes the default behavior in the Node SDK to drop HTTP spans with 401-404 and 3xx status codes by default to reduce noise in tracing data.

Other Changes

• core: Prepend vercel ai attributes with vercel.ai.X

• nextjs: Add disableSentryWebpackConfig flag

• nextjs: Build app manifest

• nextjs: Inject manifest into client for turbopack builds

• nextjs: Inject manifest into client for webpack builds

• node-native: Add option to disable event loop blocked detection

• react-router: Ensure http.server route handling is consistent

• core: Avoid prolonging idle span when starting standalone span

• core: Remove side-effect from tracing/errors.ts

• core: Wrap beforeSendLog in consoleSandbox

• node-core: Apply correct SDK metadata

• react-router: Ensure that all browser spans have source=route

Work in this release was contributed by @janpapenbrock. Thank you for your contribution!