This is the first release candidate of version 11 of the Sentry JavaScript SDKs.

We recommend following the migration guide to upgrade from version 10 to version 11.

Breaking Changes

All SDKs

• feat: Remove support for initialising via --require (#22513)
• feat!: Rename deprecated http.* span attributes (#23574)
• feat!: Rename deprecated net. span attributes (#23301)
• feat!: Replace skipOpenTelemetrySetup with enableOpenTelemetrySetup (#23199)
• feat!: Replace the deprecated http.target span attribute (#23575)
• feat!: Require Node >=20.19.0 as minimum supported version (#22558)
• feat!: Use handler span op for terminal request handlers (#22871)
• feat!: Use middleware span op for web-server middleware (#22852)
• feat(frameworks)!: Use function op for framework functions (#23047)
• feat(node/cloudflare)!: Remove deprecated honoIntegration (#22480)
• feat(v11): Drop TypeScript 3.8 support (#18604)

AI integrations

• feat(langchain): Emit gen_ai.pipeline.name instead of langchain.chain.name (#23740)
• ref(anthropic)!: Move Anthropic AI integration to @sentry/server-utils (#22954)
• ref(google-genai)!: Move Google GenAI integration to @sentry/server-utils (#22959)
• ref(langchain)!: Move LangChain and LangGraph integrations to @sentry/server-utils (#22962)
• ref(langgraph)!: Drop gen_ai.create_agent spans (#22840)
• ref(openai)!: Move OpenAI AI integration to @sentry/server-utils (#22953)
• ref(vercel-ai)!: Move Vercel AI integration to @sentry/server-utils (#22964)
• ref(workers-ai)!: Move Workers AI integration to @sentry/server-utils (#22960)

@sentry/angular

• feat(angular,ember,sveltekit)!: Use router span op for frontend routers (#23086)
• feat(angular)!: Use ui.mount and function span ops for tracing decorators (#22667)

@sentry/astro

• feat(astro)!: Drop support for Astro 3 (#22683)
• feat(astro)!: Enable orchestrion instrumentation on Cloudflare Workers (#23003)
• feat(astro)!: Remove deprecated sourceMapsUploadOptions build option (#23630)
• feat(astro)!: Remove unstable_sentryVitePluginOptions (#23370)
• ref(astro)!: Migrate import hook to makeOrchestrionLoader (#22861)
• ref(astro)!: Remove deprecated release/debug conflict workaround from BuildTimeOptionsBase (#23270)

@sentry/aws-serverless

• chore(aws-serverless)!: Drop nodejs18.x from the Lambda layer runtimes (#23155)
• feat(aws-serverless): Remove deprecated disableAwsContextPropagation option (#23170)
• feat(aws-serverless)!: Emit faas.invocation_id and cloud.resource_id (#24384)
• feat(aws-serverless)!: Remove unused startTrace option and tryPatchHandler (#23219)
• feat(aws-serverless)!: Use function.aws span op for Lambda invocations (#22677)
• feat(aws)!: Use queue Span OP for AWS SQS & SNS messaging (#23757)
• ref(aws-serverless)!: Migrate import hook to makeOrchestrionLoader (#22862)

@sentry/browser

• chore(browser)!: Remove legacy profiling option profilesSampleRate (#23220)
• feat(browser)!: Do not include metrics in base CDN bundle (#23207)
• feat(browser)!: drop browser support for AI integrations (#22438)
• feat(browser)!: Extract performance.{mark,measure} spans into new userTimingSpansIntegration (#22554)
• feat(browser)!: Extract interaction spans into new interactionsIntegration (#23295)
• feat(browser)!: Record console breadcrumbs via consoleIntegration (#24387)
• feat(browser)!: Rename bfcacheIntegration to bfcacheMetricsIntegration (#23776)
• feat(browser)!: Report web vitals for bfcache restores by default (#24325)
• feat(browser)!: Send session status unhandled instead of crashed for unhandled errors (#22475)
• feat(browser)!: Switch default browser session lifecycle mode to page (#21245)
• feat(browser)!: Use browser.paint span op for paint entries (#22673)
• fix(browser)!: stop tagging DOMException.code on events (#23992)
• fix(browser)!: Use snake_case consistently for ops (#23100)
• ref(browser): Remove deprecated trackFetchStreamPerformance flag (#23172)
• ref(browser)!: Drop Safari 14 support - remove navigationStart fallback and pagehide listeners (#21293)
• ref(browser)!: Remove beforeSpanEnd callback in favor of beforeIdleSpanEnd hook (#22818)

@sentry/bundler-plugins

• feat(bundler-plugins)!: Migrate from @sentry/cli to the sentry CLI SDK (#23398)

@sentry/cloudflare

• feat(cf/vercel-edge)!: Align request data collection with v11 defaults (#22850)
• feat(cloudflare)!: Auto-instrument the Worker by default in the Vite plugin (#23273)
• feat(cloudflare)!: Enable build-time instrumentation by default in Vite plugin (#22950)
• feat(cloudflare)!: Make the nodejs_compat entrypoint the default (#22900)
• feat(cloudflare)!: Match rpcTracePropagationBindings case-insensitively (#23625)
• feat(cloudflare)!: Replace enableRpcTracePropagation with rpcTracePropagationBindings (#23486)
• feat(cloudflare)!: Skip rate limit spans (#23907)
• feat(cloudflare)!: Use function span op for cron, email and workflow steps (#22703)
• ref(cloudflare)!: Remove deprecated instrumentD1WithSentry export (#23153)
• ref(cloudflare)!: Remove instrumentPrototypeMethods option (#22961)
• ref(cloudflare)!: Remove wrapRequestHandler from main entrypoint (#22881)
• ref(cloudflare)!: Use shared SentryTracerProvider for OpenTelemetry interop (#23300)

@sentry/core

• feat(core): Remove span from ScopeData (#23225)
• feat(core)!: Align request data collection with v11 defaults (#22853)
• feat(core)!: Default attachStacktrace to true (#22572)
• feat(core)!: Enable data collection by default (#22917)
• feat(core)!: Enable logs by default (#22630)
• feat(core)!: Enable span streaming by default ([#22642](#22642...

Important Changes

• feat(v10/effect): Capture errors through the Effect v4 ErrorReporter API (#24445)

  On Effect v4, Sentry.effectLayer now registers a Sentry ErrorReporter. Failures that pass through Effect.withErrorReporting, ErrorReporter.report or the built-in HTTP and RPC reporting boundaries are captured automatically, with ErrorReporter.ignore, ErrorReporter.severity and ErrorReporter.attributes annotations respected. Nothing changes on Effect v3.

Other Changes

• feat(v10/core): Accept a CollectBehavior shorthand for dataCollection.httpHeaders (#24339)
• fix(v10/browser): Release the XHR virtualError once the request completed (#24307)
• fix(v10/browser-utils): Skip nullish LCP entries in vendored web-vitals (#24349)
• fix(v10/bundler-plugins): Stamp debug IDs onto emitted source maps when disable-upload is set (#24332)
• fix(v10/core): Don't instrument the SDK's own envelope requests (#24276)
• fix(v10/nextjs): Only include emitted chunk directories in Turbopack sourcemap upload (#24295)
• fix(v10/nitro): Import from nitro/h3 instead of h3 directly (#24444)
• fix(v10/node-core): Don't recurse in logAndExitProcess on a broken stdio pipe (#24353)
• fix(v10/nuxt): Detect Nitro version via the app's Nuxt dependency chain (#24025)
• fix(v10/replay): Don't rewrite already-emitted nodes when syncing mirror attributes (#23588)

Bundle size 📦

This is a beta release of the upcoming major release of version 11.
This release does not yet entail a comprehensive changelog as version 11 is not yet stable.

For this release's iteration of the migration guide, see the Migration Guide as per 11.0.0-beta.2.

Please note that the migration guide is work in progress and subject to change.

Bundle size 📦

• feat(v10): Streamline isolation scope handling & reset in isolation scopes (#24152)
• fix(server-utils): Include Gemini reasoning tokens in Vercel AI token usage (#23433)
• fix(v10/browser): Set user_agent.original on all spans for consistent filtering (#24226)
• fix(v10/cloudflare): Auto-instrument classes re-exported from the worker entry (#24181)
• fix(v10/core): Guard loadModule default parameter against ESM scope (#24154)
• fix(v10/core): Match wrapped Facebook Mobile browser errors in DEFAULT_IGNORE_ERRORS (#23877)
• fix(v10/core): Resolve MCP capture policy per operation (#23796)
• fix(v10/nextjs): Fix SDK import crashing under jsdom/happy-dom (#23906)
• fix(v10/nextjs): Keep the Pages Router runtime out of App Router client bundles (#24223)
• fix(v10/nextjs): Register Vercel AI span processors on Next.js (#23773)
• fix(v10/nuxt): Windows file:// for import-in-the-middle hook and isAbsolute for C:\ (#24026)
• fix(v10/profiling-node): Bump @sentry/node-cpu-profiler to 2.4.4 (#24238)
• fix(v10/sveltekit): Handle SvelteKit 3 error kinds in handleErrorWithSentry (#23995)
• fix(v10/sveltekit): Read Cloudflare execution context from platform.ctx (#23994)
• fix(v10/sveltekit): Read SvelteKit config from the Vite plugin (#23998)

Work in this release was contributed by @halillusion and @zkasuran. Thank you for your contributions!

Bundle size 📦

This is a beta release of the upcoming major release of version 11.
This release does not yet entail a comprehensive changelog as version 11 is not yet stable.

For this release's iteration of the migration guide, see the Migration Guide as per 11.0.0-beta.1.

Please note that the migration guide is work in progress and subject to change.

Bundle size 📦

This is a beta release of the upcoming major release of version 11.
This release does not yet entail a comprehensive changelog as version 11 is not yet stable.

For this release's iteration of the migration guide, see the Migration Guide as per 11.0.0-beta.0.

Please note that the migration guide is work in progress and subject to change.

Bundle size 📦

Important Changes

• feat(v10/nextjs): Add @sentry/nextjs/config entry point (#23766)

  withSentryConfig is now available from @sentry/nextjs/config, the path it moves to in v11. Importing it from @sentry/nextjs still works on v10 but logs a warning once, so you can change your next.config file today and upgrade to v11 without touching it again.

  // next.config.mjs
  - import { withSentryConfig } from '@sentry/nextjs';
  + import { withSentryConfig } from '@sentry/nextjs/config';

Other Changes

• feat(v10/node): Deprecate shouldHandleError on setupExpressErrorHandler and setupFasitfyErrorHandler (#23734)
• fix(v10/cloudflare): Instrument Durable Object handlers installed as read-only properties (#23769)

Bundle size 📦

This is an alpha release of the upcoming major release of version 11.
This release does not yet entail a comprehensive changelog as version 11 is not yet stable.

For this release's iteration of the migration guide, see the Migration Guide as per 11.0.0-alpha.2.

Please note that the migration guide is work in progress and subject to change.

Bundle size 📦

Important Changes

• AI integrations no longer report errors that propagate to the caller (#23638, #23639, #23640)

  Across all AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, and LangGraph), the SDK no longer sends an event to Sentry for errors that the AI framework propagates to your code. Previously the instrumentation reported these as unhandled (handled: false) before your own error handling ran, so an error your code caught still showed up in Sentry as an unhandled crash. The span is still marked as errored and the error still propagates, so reporting is left to your application: if your code does not handle the error, it reaches Sentry's global error handlers and is captured as unhandled, just like any other uncaught error. Errors that a provider surfaces as data on an otherwise successful response (such as Anthropic error-shaped responses or Google GenAI blocked content) are still captured, since your code never sees them propagate.

• feat(v10/cloudflare): Add rpcTracePropagationBindings (#23737, #23738)

  The new rpcTracePropagationBindings option names the env bindings that outgoing RPC calls propagate trace context to. Strings match a binding name exactly, regular expressions match by pattern, and the default empty array propagates to nothing. RPC has no headers to carry trace context, so the SDK appends it as a trailing argument that only a Sentry-instrumented receiver removes again. List only the bindings whose receiver you know runs Sentry. Setting the option takes precedence over enableRpcTracePropagation, which is now deprecated. When you build with the Sentry Cloudflare Vite plugin, the bindings that resolve to this worker (its own Durable Objects and self service bindings) are derived from your wrangler config and added for you.

Other Changes

• fix(v10/astro): support astro v7 route patterns properly (#23657)
• fix(v10/bundler-plugins): Preserve full file path in component annotation source maps (#23595)
• fix(v10/core): Store child span timeout handle in _childSpanTimeoutID (#23673)
• fix(v10/node): Only end the process session when it is still ok (#23731)
• fix(v10/react-router): Use react-router's own instrumentation types instead of a mirrored copy (#23589)
• fix(v10/replay): Suppress Worker destroyed error on session expiry (#23654)
• fix(v10/server-utils): Keep orchestrion registration out of tree-shaking (#23591)
• fix(v10/server-utils): Stop shipping orchestrion bundler plugins as production dependencies (#23667)
• fix(v10/server-utils): Support openai v7 in auto-instrumentation (#23713)
• fix(v10/sveltekit): Detect native tracing in flattened SvelteKit 3 config (#23656)

Work in this release was contributed by @ryanrho-mercor, @lux-in-tenebris-lucet, and @suhailopensource. Thank you for your contributions!

Bundle size 📦

Important Changes

• feat(v10/core)!: Enable logs by default (#23311)

The enableLogs client option now defaults to true, so Sentry Logs work without any manual opt-in. Nothing is captured unless you call the Sentry.logger.* APIs or add a log-forwarding integration (such as consoleLoggingIntegration, pinoIntegration, or the winston transport), and you can set enableLogs: false to opt out. Although a default change like this would normally land in a major release, we are shipping it in a minor after careful consideration, since it sends no data on its own and only takes effect once you actively use the logging APIs or a logging integration.

Other Changes

• feat(v10/core): Deprecate scope.clear() method (#23231)
• fix(v10/core): Bound child span tracking on long-lived spans (#23406)
• fix(v10/core): Read Supabase PostgREST headers from Headers instances (#23241)
• fix(v10/hono): Use captureException from scope, not from Client (#23280)
• fix(v10/nuxt): Delete source maps after Nitro finishes building (#23508)
• fix(v10/react-router): Carry multi-byte UTF-8 across SSR stream chunk boundaries (#23421)
• fix(v10/react): Match TanStack Router pageload against the router location (#23494)

Bundle size 📦