posthog▌

### PostHog Feature Flags for Next.js - Initialize PostHog globally via instrumentation-client.ts to enable hooks without wrapping components in a provider. - Evaluate flags server-side using posthog-node and pass values as props to client components to prevent hydration mismatches and flicker. - Use useFeatureFlagEnabled or useFeatureFlagPayload hooks in client components and handle loading states for asynchronous flag data.

Automatically instrument PostHog analytics, event tracking, and feature flags across multiple frameworks. \n \n Supports JavaScript/TypeScript, React, Python, and Node.js with framework-specific setup patterns \n Covers three core capabilities: event capture with custom properties, feature flag evaluation for gradual rollouts, and user identification \n Detects existing PostHog configuration and adds instrumentation without duplicating setup \n Includes best practices for event naming convention

Event tracking, feature flags, and dashboards for product analytics with PostHog. \n \n Supports Next.js, React, Python, and Node.js with client and server-side SDKs; includes SPA pageview tracking and session management \n Event naming conventions and core tracking patterns across authentication, onboarding, feature usage, billing, and errors with React hooks for easy integration \n Feature flags with client-side hooks, server-side evaluation, and A/B testing support via payload variants \n Pro