@sentry/tracing

Important Changes

This release version bumps the internally used typescript version from 3.8.x to 4.9.x.
We use ds-downlevel to generate two versions of our types, one for >=3.8, one for >=4.9.
This means that this change should be fully backwards compatible and not have any noticable user impact,
but if you still encounter issues please let us know.

• types: Add tracePropagationTargets to top level options

Instead of passing tracePropagationTargets to the BrowserTracing integration, you can now define them on the top level:

Sentry.init({
  tracePropagationTargets: ['api.site.com'],
});

• angular: Filter out TryCatch integration by default

The Angular and Angular-ivy SDKs will not install the TryCatch integration anymore by default.
This integration conflicted with the SentryErrorHander, sometimes leading to duplicated errors and/or missing data on events.

• browser: Better event name handling for non-Error objects

When capturing non-errors via Sentry.captureException(), e.g. Sentry.captureException({ prop: "custom object" }),
we now generate a more helpful value for the synthetic exception. Instead of e.g. Non-Error exception captured with keys: currentTarget, isTrusted, target, type, you'll now get messages like:

Object captured as exception with keys: prop1, prop2
Event `MouseEvent` (type=click) captured as exception
Event `ErrorEvent` captured as exception with message `Script error.`

Other Changes

• browser: Send profiles in same envelope as transactions

• profiling: Collect timings on profiler stop calls

• replay: Do not capture replays < 5 seconds (GA)

• tracing: Add experiment to capture http timings

• tracing: Add http.response.status_code to span.data

• angular: Stop routing spans on navigation cancel and error events

• core: Only start spans in trace if tracing is enabled

• nextjs: Inject init calls via loader instead of via entrypoints

• replay: Mark ui.slowClickDetected clickCount as optional

• serverless: Export autoDiscoverNodePerformanceMonitoringIntegrations from SDK

• sveltekit: Check for cached requests in client-side fetch instrumentation

• sveltekit: Only instrument SvelteKit fetch if the SDK client is valid

• tracing: Instrument Prisma client in constructor of integration

Bundle size