fix(deps): update dependency @sentry/react to v9.14.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/react (source)	9.9.0 -> 9.14.0

---

Release Notes

getsentry/sentry-javascript (@​sentry/react)

v9.14.0

Compare Source

Important Changes

• feat: Add Supabase Integration (#​15719)

This PR adds Supabase integration to @sentry/core, allowing automatic instrumentation of Supabase client operations (database queries and authentication) for performance monitoring and error tracking.

• feat(nestjs): Gracefully handle RPC scenarios in SentryGlobalFilter (#​16066)

This PR adds better RPC exception handling to @sentry/nestjs, preventing application crashes while still capturing errors and warning users when a dedicated filter is needed. The implementation gracefully handles the 'rpc' context type in SentryGlobalFilter to improve reliability in hybrid applications.

• feat(react-router): Trace propagation (#​16070)

This PR adds trace propagation to @sentry/react-router by providing utilities to inject trace meta tags into HTML headers and offering a pre-built Sentry-instrumented request handler, improving distributed tracing capabilities across page loads.

Other Changes

• feat(deps): Bump @​prisma/instrumentation from 6.5.0 to 6.6.0 (#​16102)
• feat(nextjs): Improve server component data (#​15996)
• feat(nuxt): Log when adding HTML trace meta tags (#​16044)
• fix(node): Make body capturing more robust (#​16105)
• ref(node): Log when incoming request bodies are being captured (#​16104)

Bundle size 📦

Path	Size
@​sentry/browser	23.28 KB
@​sentry/browser - with treeshaking flags	23.12 KB
@​sentry/browser (incl. Tracing)	36.99 KB
@​sentry/browser (incl. Tracing, Replay)	74.17 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	67.55 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	78.83 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	90.65 KB
@​sentry/browser (incl. Feedback)	39.68 KB
@​sentry/browser (incl. sendFeedback)	27.9 KB
@​sentry/browser (incl. FeedbackAsync)	32.67 KB
@​sentry/react	25.09 KB
@​sentry/react (incl. Tracing)	38.91 KB
@​sentry/vue	27.51 KB
@​sentry/vue (incl. Tracing)	38.71 KB
@​sentry/svelte	23.32 KB
CDN Bundle	24.5 KB
CDN Bundle (incl. Tracing)	36.98 KB
CDN Bundle (incl. Tracing, Replay)	72 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	77.16 KB
CDN Bundle - uncompressed	71.49 KB
CDN Bundle (incl. Tracing) - uncompressed	109.34 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	220.63 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	233.16 KB
@​sentry/nextjs (client)	40.54 KB
@​sentry/sveltekit (client)	37.44 KB
@​sentry/node	143.37 KB
@​sentry/node - without tracing	96.51 KB
@​sentry/aws-serverless	120.83 KB

v9.13.0

Compare Source

Important Changes

• feat(node): Add support for winston logger (#​15983)

  Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like @sentry/nestjs). The Logging APIs in the Sentry SDK are still experimental and subject to change.

  const winston = require('winston');
  const Transport = require('winston-transport');
  
  const transport = Sentry.createSentryWinstonTransport(Transport);
  
  const logger = winston.createLogger({
    transports: [transport],
  });

• feat(core): Add wrapMcpServerWithSentry to instrument MCP servers from @modelcontextprotocol/sdk (#​16032)

  The Sentry SDK now supports instrumenting MCP servers from the @modelcontextprotocol/sdk package. Compatible with versions ^1.9.0 of the @modelcontextprotocol/sdk package.

  import { McpServer } from '@​modelcontextprotocol/sdk/server/mcp.js';
  
  // Create an MCP server
  const server = new McpServer({
    name: 'Demo',
    version: '1.0.0',
  });
  
  // Use the instrumented server in your application
  const instrumentedServer = Sentry.wrapMcpServerWithSentry(server);

• feat(core): Move console integration into core and add to cloudflare/vercel-edge (#​16024)

  Console instrumentation has been added to @sentry/cloudflare and @sentry/nextjs Edge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.

• feat(bun): Support new Bun.serve APIs (#​16035)

  Bun 1.2.6 and above have a new Bun.serve API, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.

  Thanks to @​Jarred-Sumner for helping us get this supported!

Other Changes

• feat(browser): Warn on duplicate browserTracingIntegration (#​16042)
• feat(core): Allow delayed sending with offline transport (#​15937)
• feat(deps): Bump @​sentry/webpack-plugin from 3.2.4 to 3.3.1 (#​16057)
• feat(vue): Apply stateTransformer to attachments in Pinia Plugin (#​16034)
• fix(core): Run beforeSendLog after we process log (#​16019)
• fix(nextjs): Don't show turbopack warning for newer Next.js canaries (#​16065)
• fix(nextjs): Include patch version 0 for min supported 15.3.0 (#​16026)
• fix(node): Ensure late init works with all integrations (#​16016)
• fix(react-router): Pass unstable_sentryVitePluginOptions to cli instance (#​16033)
• fix(serverless-aws): Overwrite root span name with GraphQL if set (#​16010)

v9.12.0

Compare Source

v9.11.0

Compare Source

• feat(browser): Add http.redirect_count attribute to browser.redirect span (#​15943)
• feat(core): Add consoleLoggingIntegration for logs (#​15955)
• feat(core): Don't truncate error messages (#​15818)
• feat(nextjs): Add release injection in Turbopack (#​15958)
• feat(nextjs): Record turbopack as tag (#​15928)
• feat(nuxt): Base decision on source maps upload only on Nuxt source map settings (#​15859)
• feat(react-router): Add sentryHandleRequest (#​15787)
• fix(node): Use module instead of require for CJS check (#​15927)
• fix(remix): Remove mentions of deprecated ErrorBoundary wrapper (#​15930)
• ref(browser): Temporarily add sentry.previous_trace span attribute (#​15957)
• ref(browser/core): Move all log flushing logic into clients (#​15831)
• ref(core): Improve URL parsing utilities (#​15882)

Bundle size 📦

Path	Size
@​sentry/browser	23.2 KB
@​sentry/browser - with treeshaking flags	23.02 KB
@​sentry/browser (incl. Tracing)	36.83 KB
@​sentry/browser (incl. Tracing, Replay)	73.99 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	67.39 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	78.66 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	91.22 KB
@​sentry/browser (incl. Feedback)	40.33 KB
@​sentry/browser (incl. sendFeedback)	27.83 KB
@​sentry/browser (incl. FeedbackAsync)	32.63 KB
@​sentry/react	25 KB
@​sentry/react (incl. Tracing)	38.75 KB
@​sentry/vue	27.41 KB
@​sentry/vue (incl. Tracing)	38.55 KB
@​sentry/svelte	23.23 KB
CDN Bundle	24.44 KB
CDN Bundle (incl. Tracing)	36.85 KB
CDN Bundle (incl. Tracing, Replay)	71.87 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	77.07 KB
CDN Bundle - uncompressed	71.24 KB
CDN Bundle (incl. Tracing) - uncompressed	108.94 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	220.23 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	232.8 KB
@​sentry/nextjs (client)	40.06 KB
@​sentry/sveltekit (client)	37.26 KB
@​sentry/node	142.88 KB
@​sentry/node - without tracing	96.08 KB
@​sentry/aws-serverless	120.43 KB

v9.10.1

Compare Source

• fix: Correct @​sentry-internal/feedback docs to match the code (#​15874)
• deps: Bump bundler plugins to version 3.2.4 (#​15909)

v9.10.0

Compare Source

Important Changes

• feat: Add support for logs

  • feat(node): Add logging public APIs to Node SDKs (#​15764)
  • feat(core): Add support for beforeSendLog (#​15814)
  • feat(core): Add support for parameterizing logs (#​15812)
  • fix: Remove critical log severity level (#​15824)

  All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

  Logging is gated by an experimental option, _experiments.enableLogs.

  Sentry.init({
    dsn: 'PUBLIC_DSN',
    // `enableLogs` must be set to true to use the logging features
    _experiments: { enableLogs: true },
  });
  
  const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
  
  trace('Starting database connection', { database: 'users' });
  debug('Cache miss for user', { userId: 123 });
  error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
  fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
  
  // Structured logging via the `fmt` helper function. When you use `fmt`, the string template and parameters are sent separately so they can be queried independently in Sentry.
  
  info(fmt(`Updated profile for user ${userId}`));
  warn(fmt(`Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}`));

  With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.

  const { info, warn } = Sentry.logger;
  
  info('User %s logged in successfully', [123]);
  warn('Failed to load user %s data', [123], { errorCode: 404 });

  To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.

• feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#​15821)

  The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

  const result = await Sentry.diagnoseSdkConnectivity();

  The result will be an object with the following properties:

  • "no-client-active": There was no active client when the function was called. This possibly means that the SDK was not initialized yet.
  • "sentry-unreachable": The Sentry SaaS servers were not reachable. This likely means that there is an ad blocker active on the page or that there are other connection issues.
  • undefined: The SDK is working as expected.

• SDK Tracing Performance Improvements for Node SDKs

  • feat: Stop using dropUndefinedKeys (#​15796)
  • feat(node): Only add span listeners for instrumentation when used (#​15802)
  • ref: Avoid dropUndefinedKeys for spanToJSON calls (#​15792)
  • ref: Avoid using SentryError for PromiseBuffer control flow (#​15822)
  • ref: Stop using dropUndefinedKeys in SpanExporter (#​15794)
  • ref(core): Avoid using SentryError for event processing control flow (#​15823)
  • ref(node): Avoid dropUndefinedKeys in Node SDK init (#​15797)
  • ref(opentelemetry): Avoid sampling work for non-root spans (#​15820)

  We've been hard at work making performance improvements to the Sentry Node SDKs (@sentry/node, @sentry/aws-serverless, @sentry/nestjs, etc.). We've seen that upgrading from 9.7.0 to 9.10.0 leads to 30-40% improvement in request latency for HTTP web-server applications that use tracing with high sample rates. Non web-server applications and non-tracing applications will see smaller improvements.

Other Changes

• chore(deps): Bump rrweb to 2.35.0 (#​15825)
• deps: Bump bundler plugins to 3.2.3 (#​15829)
• feat: Always truncate stored breadcrumb messages to 2kb (#​15819)
• feat(nextjs): Disable server webpack-handling for static builds (#​15751)
• fix(nuxt): Don't override Nuxt options if undefined (#​15795)

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.