@sentry/svelte

Official Sentry SDK for Svelte

This SDK currently only supports Svelte apps in the browser. If you're using SvelteKit, we recommend using our dedicated Sentry SvelteKit SDK.

General

This package is a wrapper around @sentry/browser, providing error monitoring and basic performance monitoring features for Svelte.

To use the SDK, initialize Sentry in your Svelte entry point main.js before you bootstrap your Svelte app:

// main.js / main.ts

import App from './App.svelte';

import * as Sentry from '@sentry/svelte';

// Initialize the Sentry SDK here
Sentry.init({
  dsn: '__DSN__',
  release: 'my-project-name@2.3.12',
  integrations: [Sentry.browserTracingIntegration()],

  // Set tracesSampleRate to 1.0 to capture 100%
  // of transactions for performance monitoring.
  // We recommend adjusting this value in production
  tracesSampleRate: 1.0,
});

// Then bootstrap your Svelte app
const app = new App({
  target: document.getElementById('app'),
});

export default app;

The Sentry Svelte SDK supports all features from the @sentry/browser SDK. Until it becomes more stable, please refer to the Sentry Browser SDK documentation for more information and usage instructions.

Sourcemaps and Releases

To generate source maps of your Svelte app bundle, check our guide how to configure your bundler to emit source maps.

To create releases and upload source maps to Sentry, we recommend using sentry-cli. You can for instance create a bash script to take care of creating a release, uploading source maps and finalizing the release:

#!/bin/bash

VERSION=<your version>
ORG=<your org-slug>
PROJECT=<your project-slug>

SOURCEMAPS_PATH=./dist

sentry-cli releases new $VERSION --org $ORG --project $PROJECT
sentry-cli releases files $VERSION upload-sourcemaps $SOURCEMAPS_PATH --org $ORG --project $PROJECT
sentry-cli releases finalize $VERSION  --org $ORG --project $PROJECT

Please note that the paths provided in this example work for a typical Svelte project that adheres to the project structure set by create-vite with the svelte(-ts) template. If your project setup differs from this template, your configuration may need adjustments. Please refer to our documentation of Advanced sentry-cli Sourcemaps Options and to our Sourcemaps Troubleshooting Guide.

Check out our Svelte source maps uploading guide for more information.

Changelog

8.31.0

Important Changes

• feat(node): Add dataloader integration (#13664)

This release adds a new integration for the dataloader package. The Node SDK (and all SDKs that depend on it) will now automatically instrument dataloader instances. You can also add it manually:

Sentry.init({
  integrations: [Sentry.dataloaderIntegration()],
});

Other Changes

• feat(browser): Add navigation activationStart timestamp to pageload span (#13658)
• feat(gatsby): Add optional deleteSourcemapsAfterUpload (#13610)
• feat(nextjs): Give app router prefetch requests a http.server.prefetch op (#13600)
• feat(nextjs): Improve Next.js serverside span data quality (#13652)
• feat(node): Add disableInstrumentationWarnings option (#13693)
• feat(nuxt): Adding experimental_basicServerTracing option to Nuxt module (#13643)
• feat(nuxt): Improve logs about adding Node option 'import' (#13726)
• feat(replay): Add onError callback + other small improvements to debugging (#13721)
• feat(replay): Add experimental option to allow for a checkout every 6 minutes (#13069)
• feat(wasm): Unconditionally parse instruction addresses (#13655)
• fix: Ensure all logs are wrapped with consoleSandbox (#13690)
• fix(browser): Try multiple options for lazyLoadIntegration script parent element lookup (#13717)
• fix(feedback): Actor color applies to feedback icon (#13702)
• fix(feedback): Fix form width on mobile devices (#13068)
• fix(nestjs): Preserve original function name on SentryTraced functions (#13684)
• fix(node): Don't overwrite local variables for re-thrown errors (#13644)
• fix(normalize): Treat Infinity as NaN both are non-serializable numbers (#13406)
• fix(nuxt): Use correct server output file path (#13725)
• fix(opentelemetry): Always use active span in Propagator.inject (#13381)
• fix(replay): Fixes potential out-of-order segments (#13609)

Work in this release was contributed by @KyGuy2002, @artzhookov, and @julianCast. Thank you for your contributions!