mcpField
E
error-tracking-svelte

error-tracking-svelte

github.com/posthogDevelopment7694 installsUpdated today
Repository

About error-tracking-svelte

A skill that guides developers adding PostHog error tracking to Svelte applications. It emphasizes preserving existing error handling, enabling exception autocapture first, and consulting framework-specific guidance for source maps and alerts.

Key features

  1. 01Guide PostHog error-tracking setup
  2. 02Recommend environment variables for keys
  3. 03Prioritize exception autocapture
  4. 04Provide source-map and alert references
  5. 05Recommend Svelte tools for component checks

Use cases

  1. 01Add error monitoring to a Svelte app
  2. 02Capture exceptions at error boundaries
  3. 03Investigate stack traces that lack source mapping
  4. 04Validate new or modified Svelte components

MCP support

Recommends the Svelte MCP server for consulting Svelte documentation and validating components, using documentation lookup tools and svelte-autofixer.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/posthog/skills --skill error-tracking-svelte

After installing, type/error-tracking-sveltein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
alerts.md
assigning-issues.md
fingerprints.md
monitoring.md
svelte.md
upload-source-maps.md

Details

From the project README

PostHog error tracking for Svelte

This skill helps you add PostHog error tracking to Svelte applications.

Reference files

  • references/svelte.md - Sveltekit error tracking installation - docs
  • references/fingerprints.md - Fingerprints - docs
  • references/alerts.md - Send error tracking alerts - docs
  • references/monitoring.md - Monitor and search issues - docs
  • references/assigning-issues.md - Assign issues to teammates - docs
  • references/upload-source-maps.md - Upload source maps - docs

Consult the documentation for API details and framework-specific patterns.

Key principles

  • Environment variables: Always use environment variables for PostHog keys and host URLs. Never hardcode them.
  • Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.
  • Autocapture first: Enable exception autocapture in the SDK initialization before adding manual captures.
  • Source maps: Upload source maps so stack traces resolve to original source code, not minified bundles.
  • Manual capture for boundaries: Use captureException() at error boundaries and catch blocks for errors that don't propagate to the global handler.

Framework guidelines

  • Set paths.relative to false in svelte.config.js — this is required for PostHog session replay to work correctly with SSR and is easy to miss
  • Use the Svelte MCP server tools to check Svelte documentation (list-sections, get-documentation) and validate components (svelte-autofixer) — always run svelte-autofixer on new or modified .svelte files before finishing

Comments

Markdown supported