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

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/nuxt.md

Nuxt error tracking installation (v3.7 and above) - Docs

  1. 1

    Install the PostHog Nuxt module

    Required

    Install the PostHog Nuxt module using your package manager:

    PostHog AI

    npm
    npm install @posthog/nuxt
    yarn
    yarn add @posthog/nuxt
    pnpm
    pnpm add @posthog/nuxt
    bun
    bun add @posthog/nuxt

    Add the module to your nuxt.config.ts file:

    nuxt.config.ts

    PostHog AI

    export default defineNuxtConfig({
      modules: ['@posthog/nuxt'],
      // Enable source maps generation in both vue and nitro
      sourcemap: {
        client: 'hidden'
      },
      nitro: {
        rollupConfig: {
          output: {
            sourcemapExcludeSources: false,
          },
        },
      },
      posthogConfig: {
        publicKey: '<ph_project_token>', // Find it in project settings https://app.posthog.com/settings/project
        host: 'https://us.i.posthog.com', // Optional: defaults to https://us.i.posthog.com. Use https://eu.i.posthog.com for EU region
        clientConfig: {
          capture_exceptions: true, // Enables automatic exception capture on the client side (Vue)
        },
        serverConfig: {
          enableExceptionAutocapture: true, // Enables automatic exception capture on the server side (Nitro)
        },
        sourcemaps: {
          enabled: true,
          project: '<ph_project_id>', // Your project ID from PostHog settings https://app.posthog.com/settings/environment#variables
          personalApiKey: '<ph_personal_api_key>', // Your personal API key from PostHog settings https://app.posthog.com/settings/user-api-keys (requires organization:read and error_tracking:write scopes)
          releaseName: 'my-application', // Optional: defaults to git repository name
          releaseVersion: '1.0.0', // Optional: defaults to current git commit
        },
      },
    })

    Personal API Key

    Your Personal API Key will require organization:read and error_tracking:write scopes.

    The module will automatically:

    • Initialize PostHog on both Vue (client side) and Nitro (server side)

    • Capture exceptions on both client and server

    • Generate and upload source maps during build

  2. 2

    Manually capturing exceptions

    Optional

    Our module if set up as shown above already captures both client and server side exceptions automatically.

    To send errors manually on the client side, import it and use the captureException method like this:

    Vue

    PostHog AI

    <script>
      const { $posthog } = useNuxtApp()
      if ($posthog) {
        const posthog = $posthog()
        posthog.captureException(new Error("Important error message"))
      }
    </script>

    On the server side instantiate PostHog using:

    server/api/example.js

    PostHog AI

    const runtimeConfig = useRuntimeConfig()
    const posthog = new PostHog(
      runtimeConfig.public.posthogPublicKey,
      {
        host: runtimeConfig.public.posthogHost,
      }
    );
    try {
      const results = await DB.query.users.findMany()
      return results
    } catch (error) {
      posthog.captureException(error)
    }
  3. 3

    Build your project for production

    Required

    Build your project for production by running the following command:

    Terminal

    PostHog AI

    nuxt build

    The PostHog module will automatically generate and upload source maps to PostHog during the build process.

  4. Verify error tracking

    Recommended

    Confirm events are being sent to PostHog

    Before proceeding, let's make sure exception events are being captured and sent to PostHog. You should see events appear in the activity feed.

    Image: Activity feed with eventsImage: Activity feed with events

    Check for exceptions in PostHog

  5. 4

    Upload source maps

    Required

    Great, you're capturing exceptions! If you serve minified bundles, the next step is to upload source maps to generate accurate stack traces.

    Let's continue to the next section.

    Upload source maps

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