@sentry/node

Important Changes

• nextjs: Add Turbopack support for React component name annotation

  We added experimental support for React component name annotation in Turbopack builds. When enabled, JSX elements
  are annotated with data-sentry-component, data-sentry-element, and data-sentry-source-file attributes at build
  time. This enables searching Replays by component name, seeing component names in breadcrumbs, and performance
  monitoring — previously only available with webpack builds.

  This feature requires Next.js 16+ and is currently behind an experimental flag:

  // next.config.ts
  import { withSentryConfig } from '@sentry/nextjs';
  
  export default withSentryConfig(nextConfig, {
    _experimental: {
      turbopackReactComponentAnnotation: {
        enabled: true,
        ignoredComponents: ['Header', 'Footer'], // optional
      },
    },
  });

• hono: Instrument middlewares app.use()

  Hono middleware registered via app.use() is now automatically instrumented, creating spans for each middleware invocation.

Other Changes

• node-core,node: Add tracePropagation option to http and fetch integrations

• hono: Use parametrized names for errors

• browser: Fix missing traces for user feedback

• cloudflare: Use correct Proxy receiver in instrumentDurableObjectStorage

• core: Standardize Vercel AI span descriptions to align with GenAI semantic conventions

• nextjs: Align Turbopack module metadata injection with webpack behavior

• node: Prevent duplicate LangChain spans from double module patching

• node-core,vercel-edge: Use HEROKU_BUILD_COMMIT env var for default release

• sveltekit: Fix file system race condition in source map cleaning

• tanstackstart-react: Add workerd and worker export conditions

• vercel-ai: Prevent tool call span map memory leak

Internal Changes

Work in this release was contributed by @dmmulroy, @lithdew, and @smorimoto. Thank you for your contributions!