sentry-svelte-sdk

Malicious tool definition detected

Description: + `instrumentation.server.ts` | | Server-side logging | ❌ N/A | ✅ Full — `Sentry.logger.*` in any server code | | Isolation scope per request | ❌ N/A | ✅ Set in `hooks.server.ts` for per-request context | | `consoleLoggingIntegration` | Single init | Both client and server inits | | `consola` reporter | N/A (client-only) | Server hooks or load functions | | Trace correlation | Client spans only | Client + server spans | --- ## Best Practices - Add `enableLogs: true` to **both** `hoo

Tool passed security scan

Malicious tool definition detected

--- ## Performance Considerations - Compression runs in a **Web Worker** — minimal main-thread impact - `mutationLimit` protects against DOM-heavy frameworks that trigger thousands of mutations - Network body capture is opt-in per URL — no performance cost without `networkDetailAllowUrls` - Lazy loading (`Sentry.addIntegration()`) reduces initial bundle size by ~50KB gzipped - "Errors-only" strategy (`replaysSessionSampleRate: 0`) has near-zero overhead when no error occurs --- ## Best Practices

Tool passed security scan

Malicious tool definition detected

Tool: sentry-svelte-sdk/references/error-monitoring.md [2/2] Description: from "@sentry/sveltekit"; </script> <svelte:boundary onerror={(error, reset) => { Sentry.captureException(error); }}> <RiskyComponent /> {#snippet failed(error, reset)} <p>Something went wrong.</p> <button onclick={reset}>Try again</button> {/snippet} </svelte:boundary> ``` **Tips:** - `onerror` fires synchronously before Svelte tears down the subtree — safe to call `captureException` here - `reset` re-mounts the boundary

Tool passed security scan

Tool passed security scan