@sentry/tracing

Important Changes

• remix: Add Remix v2 support

This release adds support for Remix v2 future flags, in particular for the new error handling utilities of Remix v2. We recommend you switch to using v2_errorBoundary future flag to get the best error handling experience with Sentry.

To capture errors from v2 client-side ErrorBoundary, you should define your own ErrorBoundary in root.tsx and use Sentry.captureRemixErrorBoundaryError helper to capture the error.

// root.tsx
import { captureRemixErrorBoundaryError } from "@sentry/remix";

export const ErrorBoundary: V2_ErrorBoundaryComponent = () => {
  const error = useRouteError();

  captureRemixErrorBoundaryError(error);

  return <div> ... </div>;
};

For server-side errors, define a handleError function in your server entry point and use the Sentry.captureRemixServerException helper to capture the error.

// entry.server.tsx
export function handleError(
  error: unknown,
  { request }: DataFunctionArgs
): void {
  if (error instanceof Error) {
    Sentry.captureRemixServerException(error, "remix.server", request);
  } else {
    // Optionally capture non-Error objects
    Sentry.captureException(error);
  }
}

For more details, see the Sentry Remix SDK documentation.

Other Changes

• core: Add ModuleMetadata integration

• core: Allow multiplexed transport to send to multiple releases

• tracing: Add more network timings to http calls

• tracing: Bring http timings out of experiment

• nextjs: Avoid importing SentryWebpackPlugin in dev mode

• otel: Use HTTP_URL attribute for client requests

• replay: Better session storage check

• replay: Handle errors in beforeAddRecordingEvent callback

• tracing: Improve network.protocol.version

Bundle size