@sentry/sveltekit

Official Sentry SDK for SvelteKit

Compatibility

The minimum supported version of SvelteKit is 2.0.0. The SDK works best with Vite 4.2 and newer. Older Vite versions might not generate source maps correctly.

Check our docs for SvelteKit adapter compatibility.

General

This package is a wrapper around @sentry/node for the server and @sentry/svelte for the client side, with added functionality related to SvelteKit.

Installation

To get started installing the SDK, use the Sentry Next.js Wizard by running the following command in your terminal or read the Getting Started Docs:

npx @sentry/wizard@latest -i sveltekit

The wizard will guide you throuhg logging in to Sentry and setting up the SDK. After the wizard setup is completed, the SDK will automatically capture unhandled errors, and optionally, traces and replays.

Links

• Official SDK Docs
• Sentry.io
• Sentry Discord Server
• Stack Overflow

Changelog

10.2.0

Important Changes

• feat(core): Add ignoreSpans option (#17078)

This release adds a new top-level Sentry.init option, ignoreSpans, that can be used as follows:

Sentry.init({
  ignoreSpans: [
    'partial match', // string matching on the span name
    /regex/, // regex matching on the span name
    {
      name: 'span name',
      op: /http.client/,
    },
  ],
});

Spans matching the filter criteria will not be recorded. Potential child spans of filtered spans will be re-parented, if possible.

• feat(cloudflare,vercel-edge): Add support for OpenAI instrumentation (#17338)

Adds support for OpenAI manual instrumentation in @sentry/cloudflare and @sentry/vercel-edge.

To instrument the OpenAI client, wrap it with Sentry.instrumentOpenAiClient and set recording settings.

import * as Sentry from '@sentry/cloudflare';
import OpenAI from 'openai';

const openai = new OpenAI();
const client = Sentry.instrumentOpenAiClient(openai, { recordInputs: true, recordOutputs: true });

// use the wrapped client

• ref(aws): Remove manual span creation (#17310)

The startTrace option is deprecated and will be removed in a future major version. If you want to disable tracing, set SENTRY_TRACES_SAMPLE_RATE to 0.0. instead. As of today, the flag does not affect traces anymore.

Other Changes

• feat(astro): Streamline build logs (#17301)
• feat(browser): Handles data URIs in chrome stack frames (#17292)
• feat(core): Accumulate tokens for gen_ai.invoke_agent spans from child LLM calls (#17281)
• feat(deps): Bump @prisma/instrumentation from 6.12.0 to 6.13.0 (#17315)
• feat(deps): Bump @sentry/cli from 2.50.0 to 2.50.2 (#17316)
• feat(deps): Bump @sentry/rollup-plugin from 4.0.0 to 4.0.2 (#17317)
• feat(deps): Bump @sentry/webpack-plugin from 4.0.0 to 4.0.2 (#17314)
• feat(nuxt): Do not inject trace meta-tags on cached HTML pages (#17305)
• feat(nuxt): Streamline build logs (#17308)
• feat(react-router): Add support for Hydrogen with RR7 (#17145)
• feat(react-router): Streamline build logs (#17303)
• feat(solidstart): Streamline build logs (#17304)
• fix(nestjs): Add missing sentry.origin span attribute to SentryTraced decorator (#17318)
• fix(node): Assign default export of openai to the instrumented fn (#17320)
• fix(replay): Call sendBufferedReplayOrFlush when opening/sending feedback (#17236)