@sentry/tracing

Important Changes

• Mark errors caught by the SDK as unhandled

  • feat(browser): Mark errors caught from TryCatch integration as unhandled

  • feat(integrations): Mark errors caught from HttpClient and CaptureConsole integrations as unhandled

  • feat(nextjs): Mark errors caught from NextJS wrappers as unhandled

  • feat(react): Mark errors captured from ErrorBoundary as unhandled

  • feat(remix): Mark errors caught from Remix instrumentation as unhandled

  • feat(serverless): Mark errors caught in Serverless handlers as unhandled

  • feat(vue): Mark errors caught by Vue wrappers as unhandled

This release fixes inconsistent behaviour of when our SDKs classify captured errors as unhandled.
Previously, some of our instrumentations correctly set unhandled, while others set handled.
Going forward, all errors caught automatically from our SDKs will be marked as unhandled.
If you manually capture errors (e.g. by calling Sentry.captureException), your errors will continue to be reported as handled.

This change might lead to a decrease in reported crash-free sessions and consequently in your release health score.
If you have concerns about this, feel free to open an issue.

Other Changes

• node-experimental: Implement new performance APIs

• node-experimental: Sync OTEL context with Sentry AsyncContext

• replay: Allow to configure maxReplayDuration

• remix: Add debugid injection and map deletion to sourcemaps script

• browser: Add replay and profiling options to BrowserClientOptions

• browser: Check for existence of instrumentation targets

• nextjs: Don't re-export default in route handlers

• node: Improve mysql integration

• remix: Guard against missing default export for server instrument

• deprecated

  browser: Deprecate top-level wrap function

Work in this release contributed by @SorsOps. Thank you for your contribution!

Bundle size