[CI] (c05eaeb) react-router/react-router-v7-project

[wizard-ci-bot]

Automated wizard CI run

Trigger ID: c05eaeb
App: react-router/react-router-v7-project
App directory: apps/react-router/react-router-v7-project
Workbench branch: wizard-ci-c05eaeb-react-router-react-router-v7-project
Wizard branch: main
Examples branch: main
PostHog (MCP) branch: master
Timestamp: 2026-01-14T16:19:09.831Z
Duration: 416.7s

[wizard-ci-bot]

Now I have all the information I need to provide a comprehensive PR evaluation. Let me compile the review.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router v7 application. The implementation includes client-side initialization with PostHogProvider, server-side middleware for correlating events, error tracking in ErrorBoundary, user identification on auth flows, and 12+ custom events tracking key user actions across the application. However, there are several issues with the implementation that need to be addressed.

Files changed	Lines added	Lines removed
14	+814	-38

Confidence score: 3/5 🤔

• Invalid PostHog init option: The defaults: '2025-11-30' option in entry.client.tsx is not a valid posthog-js configuration option. This should use person_profiles or similar valid options. [MEDIUM]
• ErrorBoundary calls usePostHog unconditionally during render: In root.tsx, the posthog.captureException(error) is called directly in the render function body, not in a useEffect. This violates React rules and may cause issues during SSR or error rendering. [CRITICAL]
• Country detail tracking outside useEffect: In country.tsx, the tracking logic uses a ref but is executed in the component body, not in a useEffect, which could lead to multiple captures in strict mode or unexpected behavior. [MEDIUM]
• Reverse proxy only works in dev server: The Vite proxy config in vite.config.ts only applies during development, not in production builds. [MEDIUM]

---

File changes

Filename	Score	Description
app/entry.client.tsx	3/5	PostHog client initialization with invalid defaults option; __add_tracing_headers is an internal option
app/lib/posthog-middleware.ts	4/5	Server-side middleware for event correlation; creates new PostHog instance per request with proper shutdown
app/root.tsx	2/5	Error tracking in ErrorBoundary but called during render instead of in useEffect, violating React rules
app/routes/countries.tsx	4/5	Good event tracking for claim/like/visit/search/filter with relevant properties; well-structured handlers
app/routes/country.tsx	3/5	Detail view tracking but uses ref-based tracking outside useEffect which is not ideal
app/routes/home.tsx	4/5	CTA click tracking with proper navigation; changed Link to button (minor behavioral change)
app/routes/login.tsx	4/5	User identification and login success/failure tracking with appropriate properties
app/routes/profile.tsx	5/5	Logout tracking with posthog.reset() to clear identity - correct implementation
app/routes/signup.tsx	4/5	User signup tracking with identify and exception capture; includes email in identify (PII consideration)
package.json	5/5	Correct PostHog dependencies added: @posthog/react, posthog-js, posthog-node
react-router.config.ts	5/5	Properly enables v8_middleware future flag for middleware support
vite.config.ts	3/5	SSR noExternal config correct; proxy only works in dev, not production

---

App sanity check: 3/5 ⚠️

Criteria	Result	Description
App builds and runs	Likely Yes	Dependencies added correctly, but potential runtime issues with ErrorBoundary
Preserves existing env vars & configs	Yes	Adds new VITE_PUBLIC_POSTHOG_KEY and VITE_PUBLIC_POSTHOG_HOST env vars
No syntax or type errors	Likely Yes	Code appears syntactically correct
Correct imports/exports	Yes	All imports properly added from @posthog/react and posthog packages
Minimal, focused changes	Yes	Changes focused on PostHog integration with minimal refactoring

Issues

• ErrorBoundary hook violation: usePostHog() is called and captureException is invoked directly in the render body of ErrorBoundary, not in a useEffect. This could cause issues during SSR, multiple calls, or error during error rendering. Move to useEffect or use the built-in PostHogErrorBoundary component. [CRITICAL]
• Invalid init option: The defaults: '2025-11-30' is not a valid posthog-js option and will be ignored or cause warnings. [MEDIUM]
• Home page Link changed to button: The "Explore Now" CTA was changed from a <Link> to a <button> with navigate(). This changes SEO behavior and removes accessibility benefits of native anchor tags. [LOW]

Other completed criteria

• SSR compatibility configured in Vite with noExternal for PostHog packages
• Future flag enabled for React Router v8 middleware
• Server middleware properly shuts down PostHog client after each request

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js, posthog-node, @posthog/react all installed
PostHog client initialized	Partial	Client initialized in entry.client.tsx with PostHogProvider, but uses invalid defaults option
capture()	Yes	Multiple capture calls across routes for user actions
identify()	Yes	User identification on login (username) and signup (userId + traits)
Error tracking	Partial	captureException used in ErrorBoundary and signup, but ErrorBoundary implementation is incorrect
Reverse proxy	Partial	Vite dev server proxy configured for /ingest, but not functional in production

Issues

• Invalid defaults option: defaults: '2025-11-30' in posthog.init() is not a recognized configuration option. This should be removed or replaced with valid options like person_profiles. [MEDIUM]
• ErrorBoundary captureException in render: The exception capture happens during render, not in an effect, which is incorrect React usage and may fail silently or cause double-captures. [CRITICAL]
• Reverse proxy incomplete: The Vite proxy only works in development. Production deployments will still send directly to PostHog servers, defeating adblock circumvention. Need server-side proxy configuration or rewrites in deployment platform. [MEDIUM]
• __add_tracing_headers internal option: Using __add_tracing_headers is an internal/undocumented option that may break in future versions. [LOW]

Other completed criteria

• PostHogProvider wraps the entire app at the client entry point
• Server middleware uses posthog-node with proper session/distinct ID correlation from headers
• User reset on logout with posthog.reset()
• API host configured via environment variable

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
login.tsx	user_logged_in, login_failed	Authentication tracking with username; good for conversion funnel
signup.tsx	user_signed_up, captureException	New user acquisition tracking with email traits
profile.tsx	user_logged_out	Session end tracking with engagement stats (points, countries claimed)
countries.tsx	country_search, region_filter_changed, country_claimed, country_liked, country_visited	Core engagement events with relevant properties (region, counts)
country.tsx	country_detail_viewed	Detail page funnel tracking with country metadata
home.tsx	explore_cta_clicked	Homepage conversion CTA tracking
root.tsx	captureException	Error tracking (though implementation is flawed)

Issues

• Email in signup identify: The signup identify call includes email as a user property. Depending on privacy requirements, this could be considered PII. Consider if this is necessary or should be hashed. [LOW]

Other completed criteria

• Events capture meaningful user actions (claim, like, visit countries)
• Search and filter events capture intent and behavior
• Properties enriched with context (region, counts, previous values)
• Events support building funnels: homepage CTA → country list → country detail → country action
• Authentication events enable cohort analysis (new users vs returning)

---

Reviewed by wizard workbench PR evaluator