> **error-tracking-web** — chapter 100 of 200 in [PostHog/skills](https://skillsdocs.com/PostHog/skills).
>
> Book (all chapters, one file): https://skillsdocs.com/PostHog/skills.md
> Machine manifest: https://skillsdocs.com/PostHog/skills/.well-known/agent-skills/index.json
> Install the book: `npx skills add PostHog/skills`
> Upstream: https://github.com/PostHog/skills/blob/main/skills/posthog/all/skills/error-tracking-web/SKILL.md @ `main`
> Raw bytes, no header: https://raw.githubusercontent.com/PostHog/skills/main/skills/posthog/all/skills/error-tracking-web/SKILL.md
> Base for relative paths: https://raw.githubusercontent.com/PostHog/skills/main/skills/posthog/all/skills/error-tracking-web/
> Licence: MIT — https://spdx.org/licenses/MIT.html
>
> Bundled files (6), referenced from this skill's directory:
>   - `references/alerts.md` — https://raw.githubusercontent.com/PostHog/skills/main/skills/posthog/all/skills/error-tracking-web/references/alerts.md
>   - `references/assigning-issues.md` — https://raw.githubusercontent.com/PostHog/skills/main/skills/posthog/all/skills/error-tracking-web/references/assigning-issues.md
>   - `references/fingerprints.md` — https://raw.githubusercontent.com/PostHog/skills/main/skills/posthog/all/skills/error-tracking-web/references/fingerprints.md
>   - `references/monitoring.md` — https://raw.githubusercontent.com/PostHog/skills/main/skills/posthog/all/skills/error-tracking-web/references/monitoring.md
>   - `references/upload-source-maps.md` — https://raw.githubusercontent.com/PostHog/skills/main/skills/posthog/all/skills/error-tracking-web/references/upload-source-maps.md
>   - `references/web.md` — https://raw.githubusercontent.com/PostHog/skills/main/skills/posthog/all/skills/error-tracking-web/references/web.md
>
> Content © its authors, served unmodified. Takedown: https://github.com/kyleledbetter/skillsdocs/issues/new?labels=takedown&title=Takedown+request

<!-- Verbatim upstream SKILL.md follows, YAML frontmatter included. -->

---
name: error-tracking-web
description: PostHog error tracking for Web (JavaScript)
metadata:
  author: PostHog
  version: 1.9.4
---

# PostHog error tracking for Web (JavaScript)

This skill helps you add PostHog error tracking to Web (JavaScript) applications.

## Reference files

- `references/web.md` - Web error tracking installation - 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

- Remember that source code is available in the node_modules directory
- Check package.json for type checking or build scripts to validate changes
- posthog-js is the JavaScript SDK package name
- posthog.init() MUST be called before any other PostHog methods (capture, identify, etc.)
- posthog-js is browser-only — do NOT import it in Node.js or server-side contexts (use posthog-node instead)
- Autocapture is ON by default with posthog-js (tracks clicks, form submissions, pageviews). Do NOT disable autocapture unless the user explicitly requests it.
- NEVER send PII in posthog.capture() event properties — no emails, full names, phone numbers, physical addresses, IP addresses, or user-generated content
- PII belongs in posthog.identify() person properties (email, name, role), NOT in capture() event properties
- Call posthog.identify(userId, { email, name, role }) on login AND on page refresh if the user is already logged in
- Call posthog.reset() on logout to unlink future events from the current user
- For SPAs without a framework router, capture pageviews with posthog.capture($pageview) or use the capture_pageview history_change option in init for History API routing