PostHogofficial

integration-react-tanstack-router-code-based

PostHog/skills · updated Apr 10, 2026

$npx skills add https://github.com/PostHog/skills --skill integration-react-tanstack-router-code-based
0 commentsdiscussion
summary

### PostHog Integration for TanStack Router

  • Initialize PostHogProvider in the root route to ensure global access to the analytics client across all child routes.
  • Track pageviews using TanStack Router navigation events and capture user actions directly within event handlers, avoiding useEffect.
  • Identify users during authentication and maintain session correlation by passing distinct IDs via headers in API requests.
skill.md

PostHog integration for React with TanStack Router (code-based)

This skill helps you add PostHog analytics to React with TanStack Router (code-based) applications.

Workflow

Follow these steps in order to complete the integration:

  1. basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start here
  2. basic-integration-1.1-edit.md - PostHog Setup - Edit
  3. basic-integration-1.2-revise.md - PostHog Setup - Revise
  4. basic-integration-1.3-conclude.md - PostHog Setup - Conclusion

Reference files

  • references/EXAMPLE.md - React with TanStack Router (code-based) example project code
  • references/tanstack-start.md - Tanstack start - docs
  • references/identify-users.md - Identify users - docs
  • references/basic-integration-1.0-begin.md - PostHog setup - begin
  • references/basic-integration-1.1-edit.md - PostHog setup - edit
  • references/basic-integration-1.2-revise.md - PostHog setup - revise
  • references/basic-integration-1.3-conclude.md - PostHog setup - conclusion

The example project shows the target implementation pattern. Consult the documentation for API details.

Key principles

  • Environment variables: Always use environment variables for PostHog keys. Never hardcode them.
  • Minimal changes: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.
  • Match the example: Your implementation should follow the example project's patterns as closely as possible.

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)
  • Use TanStack Router's built-in navigation events for pageview tracking instead of useEffect
  • Use PostHogProvider in the root component defined in either the file-based convention (__root.tsx) or code-based convention (wherever createRootRoute() is called) so all child routes have access to the PostHog client

Identifying users

Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers to maintain correlation.

Error tracking

Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.629 reviews
  • Shikha Mishra· Dec 24, 2024

    integration-react-tanstack-router-code-based fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ganesh Mohane· Dec 16, 2024

    Keeps context tight: integration-react-tanstack-router-code-based is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Isabella Farah· Dec 12, 2024

    integration-react-tanstack-router-code-based reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Li Li· Dec 4, 2024

    integration-react-tanstack-router-code-based is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Chen Haddad· Nov 23, 2024

    Solid pick for teams standardizing on skills: integration-react-tanstack-router-code-based is focused, and the summary matches what you get after install.

  • Sakshi Patil· Nov 7, 2024

    integration-react-tanstack-router-code-based has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Zaid Iyer· Nov 3, 2024

    I recommend integration-react-tanstack-router-code-based for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Chaitanya Patil· Oct 26, 2024

    Solid pick for teams standardizing on skills: integration-react-tanstack-router-code-based is focused, and the summary matches what you get after install.

  • Fatima Flores· Oct 22, 2024

    Useful defaults in integration-react-tanstack-router-code-based — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kofi Robinson· Oct 14, 2024

    integration-react-tanstack-router-code-based has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 29

1 / 3