AutoGineer
Generated banner for Error Tracking Nuxt
Generated logo for Error Tracking Nuxt

Error Tracking Nuxt

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

PostHog error tracking for Nuxt
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides guidance on implementing PostHog error tracking within Nuxt applications. It emphasizes maintaining existing error handling structures while leveraging PostHog's SDK for exception capture. The approach focuses on using environment variables for configuration, enabling automatic exception capture, and ensuring stack traces are readable through source map uploads.

What it does

  • Guides the integration of PostHog error tracking into Nuxt projects.
  • Provides best practices for using environment variables for sensitive configuration.
  • Explains how to enable exception autocapture for automated error reporting.
  • Details the process for uploading source maps to resolve minified stack traces.
  • Instructs on using manual capture for specific error boundaries.
  • Outlines methods for monitoring, alerting, and assigning issues to team members.

When to use it

  • When you need to monitor runtime errors in a Nuxt application.
  • When you want to centralize error reporting and issue tracking in PostHog.
  • When you need to improve debugging by resolving minified stack traces.
  • When you want to set up automated alerts for specific error spikes or new issues.

Advantages

  • Maintains existing application error handling logic without requiring major refactors.
  • Improves debugging efficiency by providing unminified stack traces.
  • Enables proactive issue management through automated assignment and alerting.
  • Supports granular filtering of errors based on event properties.

Usage examples

“How do I set up PostHog error tracking in my Nuxt 3 app?”
The agent will guide you through installing the SDK, configuring environment variables, and initializing the client to enable autocapture.
“How can I make sure my stack traces aren't minified in PostHog?”
The agent will explain the process of uploading your source maps to PostHog so that reported errors map back to your original source code.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/error-tracking-nuxt/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip error-tracking-nuxt.zip -d .agents/skills

Documentation by PostHog

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.

Files

references/fingerprints.md

Fingerprints - Docs

Every captured exception is assigned a fingerprint. This fingerprint is used to group similar exceptions into issues. This page covers how fingerprints are generated, how they're used, and how you can override them when capturing exceptions.

Fingerprint and issue grouping

Every exception has a fingerprint, whether generated or defined by the user. Each fingerprint links to exactly one issue. Exceptions that share the same fingerprint define an issue.

Multiple different fingerprints can point to the same issue (a many-to-one relationship) if you merge issues.

How are fingerprints generated?

Fingerprints are built iteratively using components of the exception event. The flowchart below shows how fingerprints are generated.

flowchart LR A[Add exception type to fingerprint] --> B{Stack trace<br/>available?} B -->|No| C[Add error message to fingerprint] C --> D[Final fingerprint] B -->|Yes| E{In-app frames<br/>exist?} E -->|No| F[Add first frame to fingerprint] E -->|Yes| G[Add in-app frame to fingerprint<br/>Priority: resolved > unresolved] F --> D G --> D

The flowchart in text

Fingerprints are generated by considering the following in combination:

  1. The exception type

  2. If there's no resolved stack trace, add the error message to the fingerprint

  3. If there are stack traces but no in-app frames (frames from your code, not a dependency), use the first frame of the stack trace

  4. If there are stack traces, in-app frames, and source maps available, use the resolved in-app stack frames

  5. If there are stack traces, in-app frames, and source maps not available, use the first in-app stack frame

In some languages, like Python, one error can trigger another, creating a chain of linked exceptions. PostHog records the entire chain in the event and generates a single fingerprint for it.

Ensuring accurate fingerprints

Resolved stack traces are critical for accurate fingerprinting. Without accurate stack traces, PostHog cannot group exceptions consistently. If you have not uploaded source maps, follow the source map guide to do so.

This also means that if the exception type or message changes from one version to the next, the fingerprint will change.

When are generated fingerprints used?

Fingerprints are used to group similar exceptions into issues automatically. Automatic issue grouping is only done when:

You can find details about how issue grouping works in the issues and exceptions guide.

Customizing fingerprints

Fingerprints can be manually set during exception capture. This is a very useful way to group exceptions that are not related to each other. You can find examples of how to do this in the custom issue grouping section.

You can also learn more about grouping issues using rules in the grouping issues guide.

Community questions

Ask a question

Was this page useful?

HelpfulCould be better

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
PostHog
Publisher
PostHog (Official)
Source
PostHog/skills · skills/posthog/error-tracking/skills/nuxt · commit a5d30e7
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
PostHog/skills

AutoGineer is not affiliated with or endorsed by PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download error-tracking-nuxt.zip