mcpField
E
error-tracking-react

error-tracking-react

github.com/posthogDevelopment76110 installsUpdated today
Repository

About error-tracking-react

A skill that guides developers through adding PostHog error tracking to React applications. It covers exception capture and source maps, alongside guidance for placing analytics in event handlers rather than effects.

Key features

  1. 01Enable exception autocapture
  2. 02Capture exceptions at error boundaries
  3. 03Upload source maps
  4. 04Track analytics in user event handlers
  5. 05Reference alerts and issue management

Use cases

  1. 01Add error monitoring to a React application
  2. 02Capture errors not reaching the global handler
  3. 03Resolve stack traces from minified code
  4. 04Record analytics when user actions occur

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/posthog/skills --skill error-tracking-react

After installing, type/error-tracking-reactin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
alerts.md
assigning-issues.md
fingerprints.md
monitoring.md
react.md
upload-source-maps.md

Details

From the project README

PostHog error tracking for React

This skill helps you add PostHog error tracking to React applications.

Reference files

  • references/react.md - React 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

  • For feature flags, use useFeatureFlagEnabled() or useFeatureFlagPayload() hooks - they handle loading states and external sync automatically
  • Add analytics capture in event handlers where user actions occur, NOT in useEffect reacting to state changes
  • Do NOT use useEffect for data transformation - calculate derived values during render instead
  • Do NOT use useEffect to respond to user events - put that logic in the event handler itself
  • Do NOT use useEffect to chain state updates - calculate all related updates together in the event handler
  • Do NOT use useEffect to notify parent components - call the parent callback alongside setState in the event handler
  • To reset component state when a prop changes, pass the prop as the component's key instead of using useEffect
  • useEffect is ONLY for synchronizing with external systems (non-React widgets, browser APIs, network subscriptions)

Comments

Markdown supported