@sentry/ember

Important Changes

• node: Add fsInstrumentation

  This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The
  integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

  This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure
  via options whether to include path arguments or error messages as span attributes when an fs call fails:

  Sentry.init({
    integrations: [
      Sentry.fsIntegration({
        recordFilePaths: true,
        recordErrorMessagesAsSpanAttributes: true,
      }),
    ],
  });

  WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of
  file I/O, like for example when running a framework dev server, including this integration can massively slow down
  your application.

Other Changes

• browser: Add spotlightBrowser integration

• browser: Allow sentry in safari extension background page

• browser: Send CLS as standalone span (experimental)

• core: Add OpenTelemetry-specific getTraceData implementation

• nextjs: Always add browserTracingIntegration

• nextjs: Always transmit trace data to the client

• nextjs: Export SentryBuildOptions

• nextjs: Update experimental_captureRequestError to reflect RequestInfo.path change in Next.js canary
  (#13344)

• nuxt: Always add tracing meta tags

• nuxt: Set transaction name for server error

• replay: Add a replay-specific logger

• sveltekit: Add bundle size optimizations to plugin options

• sveltekit: Always add browserTracingIntegration

• tracing: Make long animation frames opt-out

• astro: Correctly extract request data

• astro: Only track access request headers in dynamic page requests

• nuxt: Add import line for disabled autoImport

• nuxt: Add vue to excludeEsmLoaderHooks array

• opentelemetry: Do not overwrite http span name if kind is internal

• remix: Ensure origin is correctly set for remix server spans

Work in this release was contributed by @MonstraG, @undead-voron and @Zen-cronic. Thank you for your contributions!