Bump @sentry/sveltekit from 8.7.0 to 8.26.0 in the sentry group across 1 directory

[dependabot]

Bumps the sentry group with 1 update in the / directory: @sentry/sveltekit.

Updates @sentry/sveltekit from 8.7.0 to 8.26.0

Release notes

Sourced from @​sentry/sveltekit's releases.

8.26.0

Important Changes

• feat(node): Add fsInstrumentation (#13291)

  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

• feat(browser): Add spotlightBrowser integration (#13263)

• feat(browser): Allow sentry in safari extension background page (#13209)

• feat(browser): Send CLS as standalone span (experimental) (#13056)

• feat(core): Add OpenTelemetry-specific getTraceData implementation (#13281)

• feat(nextjs): Always add browserTracingIntegration (#13324)

• feat(nextjs): Always transmit trace data to the client (#13337)

• feat(nextjs): export SentryBuildOptions (#13296)

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

• feat(nuxt): Always add tracing meta tags (#13273)

• feat(nuxt): Set transaction name for server error (#13292)

• feat(replay): Add a replay-specific logger (#13256)

• feat(sveltekit): Add bundle size optimizations to plugin options (#13318)

• feat(sveltekit): Always add browserTracingIntegration (#13322)

• feat(tracing): Make long animation frames opt-out (#13255)

• fix(astro): Correctly extract request data (#13315)

• fix(astro): Only track access request headers in dynamic page requests (#13306)

• fix(nuxt): Add import line for disabled autoImport (#13342)

• fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)

• fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)

• fix(remix): Ensure origin is correctly set for remix server spans (#13305)

... (truncated)

Changelog

Sourced from @​sentry/sveltekit's changelog.

8.26.0

Important Changes

• feat(node): Add fsInstrumentation (#13291)

  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

• feat(browser): Add spotlightBrowser integration (#13263)

• feat(browser): Allow sentry in safari extension background page (#13209)

• feat(browser): Send CLS as standalone span (experimental) (#13056)

• feat(core): Add OpenTelemetry-specific getTraceData implementation (#13281)

• feat(nextjs): Always add browserTracingIntegration (#13324)

• feat(nextjs): Always transmit trace data to the client (#13337)

• feat(nextjs): export SentryBuildOptions (#13296)

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

• feat(nuxt): Always add tracing meta tags (#13273)

• feat(nuxt): Set transaction name for server error (#13292)

• feat(replay): Add a replay-specific logger (#13256)

• feat(sveltekit): Add bundle size optimizations to plugin options (#13318)

• feat(sveltekit): Always add browserTracingIntegration (#13322)

• feat(tracing): Make long animation frames opt-out (#13255)

• fix(astro): Correctly extract request data (#13315)

• fix(astro): Only track access request headers in dynamic page requests (#13306)

• fix(nuxt): Add import line for disabled autoImport (#13342)

• fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)

• fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)

... (truncated)

Commits

• bff9dfd release: 8.26.0
• 93fe406 Merge pull request #13351 from getsentry/prepare-release/8.26.0
• 2d4e4f5 meta: Update Changelog for 8.26.0
• 3fc12c6 fix(ci): Fix incorrect changed_any_code check in job_build (#13353)
• fd49d0b fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)
• 6c0f01a fix(ci): Bring back job skipping for PRs without code changes (#13340)
• 334f869 docs(vercel-edge): Update @sentry/vercel-edge readme to remove alpha status...
• 043ae7e feat(nextjs): Always transmit trace data to the client (#13337)
• 3871892 feat(nextjs): Update experimental_captureRequestError to reflect `RequestIn...
• e623782 fix(nuxt): Add import line for disabled autoImport (#13342)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Superseded by #2289.