@sentry/node

Important Changes

• sveltekit: Add Compatibility for builtin SvelteKit Tracing

  This release makes the @sentry/sveltekit SDK compatible with SvelteKit's native observability support introduced in SvelteKit version 2.31.0.
  If you enable both, instrumentation and tracing, the SDK will now initialize early enough to set up additional instrumentation like database queries and it will pick up spans emitted from SvelteKit.

  We will follow up with docs how to set up the SDK soon.
  For now, If you're on SvelteKit version 2.31.0 or newer, you can easily opt into the new feature:

  1. Enable experimental tracing and instrumentation support in svelte.config.js:

  2. Move your Sentry.init() call from src/hooks.server.(js|ts) to the new instrumentation.server.(js|ts) file:

     // instrumentation.server.ts
     import * as Sentry from '@sentry/sveltekit';
     
     Sentry.init({
       dsn: '...',
       // rest of your config
     });

     The rest of your Sentry config in hooks.server.ts (sentryHandle and handleErrorWithSentry) should stay the same.

  If you prefer to stay on the hooks-file based config for now, the SDK will continue to work as previously.

Other Changes

• react: Avoid multiple name updates on navigation spans

Internal Changes