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://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/alerts.md

Send error tracking alerts - Docs

To stay on top of issues, you can set up alerts. These enable you to post to Slack, Discord, Teams, or an HTTP Webhook when an issue is created or reopened.

Issue created or reopened

To alert when an issue is created or reopened, go to error tracking's configuration page and click Alerting. This shows you a list of existing alerts. Clicking New notification brings you to a page to create a new one.

Image: Error tracking alertingImage: Error tracking alerting

Choosing an option brings you to a page to configure the alert. This may require setting up the Slack integration or pasting in a webhook URL. Once done, you can test the alert by clicking Test function and then finalize by clicking Create & enable.

This will then send alerts to your chosen destination when an issue is created or reopened like this:

Issue properties and assignments

You can filter an alert based on the properties of an issue. This is useful for notifying a specific team when they have been auto assigned an issue using auto assignment rules.

Image: Error tracking alert assignee filteringImage: Error tracking alert assignee filtering

Spike alerts

PostHog can also alert you when an existing issue suddenly spikes in volume - for example, after a bad deploy. This works differently from issue-created alerts. Instead of triggering when a new issue is first seen, spike alerts fire when an issue's error rate significantly exceeds its historical baseline.

See the spike detection guide to learn how it works and how to configure it.

Other alerting options

Since error tracking works by capturing $exception events, PostHog features that trigger by events can play a role in alerts too.

Real time destinations

The first way is using real time destinations. This enables you to send events (like $exception) to other tools as soon as they are ingested.

To create a real time destination, go to the data pipelines tab in PostHog, click + New, and then select Destination. Choose your destination and press + Create.

On the destination creation screen, make sure to add an event matcher for the $exception event, filter for the properties you want, and set the trigger options.

Image: Real time destinationImage: Real time destination

Check out our real time destinations docs for more information.

Trend alerts

You can also visualize your $exception events using trends. Once you create a trend insight, click the Alerts button at the top of the insight and then New alert.

Here you can set alerts for event volume value, increase, or decrease.

Image: Insight alertImage: Insight alert

This sends an email notification to the user you choose. Check out our alerts docs for more information.

Can't find your alert?

If you'd like a destination to be added that we don't yet support, let us know in-app.

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 or PostHog.

Download ZIP

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