error-tracking-web

Integrate PostHog error tracking into JavaScript web applications.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/FrekiManagarm/dunlo --skill error-tracking-web-frekimanagarm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-tracking-web
Source: https://github.com/FrekiManagarm/dunlo/tree/main/.agents/skills/error-tracking-web
Command: npx skills add https://github.com/FrekiManagarm/dunlo --skill error-tracking-web-frekimanagarm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you reliably add PostHog error tracking to Web (JavaScript) apps so exceptions become searchable, group into issues, and can alert your team.

Core Features & Use Cases

  • Exception autocapture setup: Enable exception autocapture early so $exception events are recorded when errors happen.
  • Manual error capture at boundaries: Use captureException() in catch blocks or error boundaries for handled errors that wouldn’t reach the global handler.
  • Source maps for readable stack traces: Upload source maps so stack traces resolve to original source code rather than minified bundles.
  • Issue grouping via fingerprints: Ensure stable grouping by capturing accurate exception information and preserving stack traces where possible.

Quick Start

Install and initialize the PostHog JavaScript SDK, ensure posthog.init() runs before any captures, turn on exception autocapture, and then capture additional boundary errors with captureException() while uploading source maps during your build.

Frequently Asked Questions about error-tracking-web

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up PostHog error tracking in a JavaScript SPA?

Use captureException() inside catch blocks or error boundaries to capture handled errors, ensuring exceptions that bypass the global handler are still recorded and grouped into issues for alerting.

How do I get readable stack traces from minified JavaScript bundles?

PostHog error tracking is browser-only, so do not import server-side modules. Use safe environment-based configuration and ensure PII is never included in capture event properties to maintain privacy compliance.

What is exception autocapture and when do I need it for error tracking?

Use captureException() inside catch blocks or error boundaries to capture handled errors, ensuring exceptions that bypass the global handler are still recorded and grouped into issues for alerting.

Why are my PostHog captured exceptions not grouping into issues?

PostHog error tracking is browser-only, so do not import server-side modules. Use safe environment-based configuration and ensure PII is never included in capture event properties to maintain privacy compliance.

Do I need source maps to use PostHog error tracking in JavaScript?

PostHog error tracking is browser-only, so do not import server-side modules. Use safe environment-based configuration and ensure PII is never included in capture event properties to maintain privacy compliance.

Can I use PostHog error tracking with server-side JavaScript environments?

PostHog error tracking is browser-only, so do not import server-side modules. Use safe environment-based configuration and ensure PII is never included in capture event properties to maintain privacy compliance.