Error Tracking React
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to implementing PostHog error tracking within React applications. It emphasizes non-intrusive integration, recommending the use of environment variables for configuration and leveraging SDK autocapture features. The guide covers essential practices such as uploading source maps for readable stack traces, using manual capture for specific error boundaries, and configuring automated alerting and issue assignment workflows within the PostHog platform.
What it does
- Guides the installation and setup of PostHog error tracking in React projects.
- Provides best practices for using environment variables and SDK initialization.
- Explains how to upload source maps to resolve minified stack traces.
- Details how to implement manual error capture at specific application boundaries.
- Outlines methods for setting up automated alerts for new or spiking issues.
- Describes how to configure automatic issue assignment rules for team workflows.
When to use it
- When you need to monitor runtime errors in a React application.
- When you want to centralize error reporting and triage within PostHog.
- When you need to alert specific team members about application exceptions.
- When you need to debug production issues using unminified stack traces.
Advantages
- Non-destructive integration that complements existing error handling.
- Supports automated issue assignment based on exception properties.
- Enables proactive monitoring through spike detection alerts.
- Facilitates team collaboration by allowing issue assignment to roles or users.
Usage examples
- “How do I set up PostHog error tracking in my React app?”
- The agent will guide you through initializing the PostHog SDK, enabling exception autocapture, and ensuring your environment variables are correctly configured.
- “How can I alert my team when a specific error spikes?”
- The agent will explain how to configure spike alerts in the PostHog error tracking settings to notify your team when error rates exceed historical baselines.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/error-tracking-react/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip error-tracking-react.zip -d .agents/skills
Documentation by PostHog
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 - docsreferences/fingerprints.md- Fingerprints - docsreferences/alerts.md- Send error tracking alerts - docsreferences/monitoring.md- Monitor and search issues - docsreferences/assigning-issues.md- Assign issues to teammates - docsreferences/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)
Files
- ATTRIBUTION.mdAdded by AutoGineer960 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.2 KiB
- references/alerts.md4.1 KiB
- references/assigning-issues.md5.5 KiB
- references/fingerprints.md3.4 KiB
- references/monitoring.md8.6 KiB
- references/react.md5.4 KiB
- references/upload-source-maps.md2.7 KiB
references/react.md
React error tracking installation - Docs
1
Install the package
Required
Install
posthog-jsand@posthog/reactusing your package manager:PostHog AI
npm
npm install posthog-js @posthog/reactyarn
yarn add posthog-js @posthog/reactpnpm
pnpm add posthog-js @posthog/react2
Add environment variables
Required
Add your PostHog project token and host to your environment variables. For Vite-based React apps, use the
VITE_PUBLIC_prefix:.env
PostHog AI
VITE_PUBLIC_POSTHOG_PROJECT_TOKEN=<ph_project_token> VITE_PUBLIC_POSTHOG_HOST=https://us.i.posthog.com3
Initialize PostHog
Required
Wrap your app with the
PostHogProvidercomponent at the root of your application (such asmain.tsxif you're using Vite):main.tsx
PostHog AI
import { StrictMode } from 'react' import { createRoot } from 'react-dom/client' import './index.css' import App from './App.jsx' import { PostHogProvider } from '@posthog/react' const options = { api_host: import.meta.env.VITE_PUBLIC_POSTHOG_HOST, defaults: '2026-01-30', } as const createRoot(document.getElementById('root')).render( <StrictMode> <PostHogProvider apiKey={import.meta.env.VITE_PUBLIC_POSTHOG_PROJECT_TOKEN} options={options}> <App /> </PostHogProvider> </StrictMode> )defaults option
The
defaultsoption automatically configures PostHog with recommended settings for new projects. See SDK defaults for details.4
Accessing PostHog in your code
Recommended
Use the
usePostHoghook to access the PostHog instance in any component wrapped byPostHogProvider:MyComponent.tsx
PostHog AI
import { usePostHog } from '@posthog/react' function MyComponent() { const posthog = usePostHog() function handleClick() { posthog.capture('button_clicked', { button_name: 'signup' }) } return <button onClick={handleClick}>Sign up</button> }You can also import
posthogdirectly for non-React code or utility functions:utils/analytics.ts
PostHog AI
import posthog from 'posthog-js' export function trackPurchase(amount: number) { posthog.capture('purchase_completed', { amount }) }5
Send events
Recommended
Click around and view a couple pages to generate some events. PostHog automatically captures pageviews, clicks, and other interactions for you.
If you'd like, you can also manually capture custom events:
JavaScript
PostHog AI
posthog.capture('my_custom_event', { property: 'value' })6
Set up exception autocapture
Recommended
You can enable exception autocapture for the JavaScript Web SDK in the Error tracking section of your project settings.
When enabled, this automatically captures
$exceptionevents when errors are thrown by wrapping thewindow.onerrorandwindow.onunhandledrejectionlisteners.7
Set up error boundaries
Optional
You can use the
PostHogErrorBoundarycomponent to capture rendering errors thrown by components:JavaScript
PostHog AI
import { PostHogProvider, PostHogErrorBoundary } from '@posthog/react' const Layout = () => { return ( <PostHogProvider apiKey="<ph_project_token>"> <PostHogErrorBoundary fallback={<YourFallbackComponent />} // (Optional) Add a fallback component that's shown when an error happens. > <YourApp /> </PostHogErrorBoundary> </PostHogProvider> ) } const YourFallbackComponent = ({ error, componentStack, exceptionEvent }) => { return <div>Something went wrong. Please try again later.</div> }8
Manually capture exceptions
Optional
It is also possible to manually capture exceptions using the
captureExceptionmethod:JavaScript
PostHog AI
posthog.captureException(error, additionalProperties)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
9
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.
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/react · 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-react.zip