mcpField
E
error-tracking-nuxt

error-tracking-nuxt

github.com/posthogDevelopment7693 installsUpdated today
Repository

About error-tracking-nuxt

A skill for adding PostHog error tracking to Nuxt applications. It guides implementation using existing error handling, SDK autocapture, source maps, and manual capture at boundaries.

Key features

  1. 01Nuxt error tracking setup
  2. 02Exception autocapture guidance
  3. 03Source map upload guidance
  4. 04Manual exception capture
  5. 05Environment variable configuration

Use cases

  1. 01Add PostHog tracking to a Nuxt app
  2. 02Improve stack traces with source maps
  3. 03Capture errors missed by global handlers

Install

Copy the command and run it in a terminal.

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

After installing, type/error-tracking-nuxtin 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
nuxt.md
upload-source-maps.md

Details

From the project README

PostHog error tracking for Nuxt

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

Reference files

  • references/nuxt.md - Nuxt error tracking installation (v3.7 and above) - 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

No specific framework guidelines.

Comments

Markdown supported