@sentry-internal/feedback

Sentry Integration for Feedback

This SDK is considered experimental and in a beta state. It may experience breaking changes, and may be discontinued at any time. Please reach out on GitHub if you have any feedback/concerns.

To view Feedback in Sentry, your Sentry organization must be an early adopter.

Installation

Please read the offical integration documentation for installation instructions.

Configuration

The Feedback integration is highly customizable, please read the official integration documentation for the most up-to-date configuration options.

Changelog

8.6.0

Important Changes

• feat(metrics): Add timings method to metrics (#12226)

  This introduces a new method, metrics.timing(), which can be used in two ways:

  1. With a numeric value, to simplify creating a distribution metric. This will default to second as unit:

  Sentry.metrics.timing('myMetric', 100);
  

  1. With a callback, which will wrap the duration of the callback. This can accept a sync or async callback. It will create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:

  const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction);
  

• feat(react): Add Sentry.reactErrorHandler (#12147)

  This PR introduces Sentry.reactErrorHandler, which you can use in React 19 as follows:

  import * as Sentry from '@sentry/react';
  import { hydrateRoot } from 'react-dom/client';
  
  ReactDOM.hydrateRoot(
    document.getElementById('root'),
    <React.StrictMode>
      <App />
    </React.StrictMode>,
    {
      onUncaughtError: Sentry.reactErrorHandler(),
      onCaughtError: Sentry.reactErrorHandler((error, errorInfo) => {
        // optional callback if users want custom config.
      }),
    },
  );
  

  For more details, take a look at the PR. Our documentation will be updated soon!

Other Changes

• feat(sveltekit): Add request data to server-side events (#12254)
• fix(core): Pass in cron monitor config correctly (#12248)
• fix(nextjs): Don't capture suspense errors in server components (#12261)
• fix(tracing): Ensure sent spans are limited to 1000 (#12252)
• ref(core): Use versioned carrier on global object (#12206)