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

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: a283762
App: react-router/react-router-v7-project
App directory: apps/react-router/react-router-v7-project
Workbench branch: wizard-ci-a283762-react-router-react-router-v7-project
Wizard branch: main
Examples branch: main
PostHog (MCP) branch: master
Timestamp: 2026-01-15T22:37:43.148Z
Duration: 345.7s

[wizard-ci-bot]

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router v7 Framework mode project. It adds client-side tracking via posthog-js and @posthog/react, server-side middleware using posthog-node, user identification on auth flows, error tracking in the error boundary, and custom event tracking for key user interactions. The implementation includes a development-only reverse proxy configuration.

Files changed	Lines added	Lines removed
13	+756	-22

Confidence score: 3/5 🤔

• Invalid PostHog init option: defaults: '2025-11-30' is not a valid PostHog configuration option - should be person_profiles: 'identified_only' or similar valid option [CRITICAL]
• Reverse proxy only works in dev: The Vite proxy configuration only applies during development (vite dev), not in production builds. Production deployments will not benefit from adblock circumvention [MEDIUM]
• Hooks called unconditionally in ErrorBoundary: usePostHog() is called at the top of ErrorBoundary which may execute during rendering, potentially causing issues with React's rules of hooks during error states [MEDIUM]

---

File changes

Filename	Score	Description
app/entry.client.tsx	3/5	PostHog initialization with invalid defaults option; correctly wraps app with PostHogProvider
app/lib/posthog-middleware.ts	4/5	Server-side middleware for session correlation; proper shutdown handling
app/root.tsx	3/5	Adds middleware export and error tracking; hook usage in ErrorBoundary is questionable
app/routes/countries.tsx	4/5	Good event tracking for user actions (claim, like, visit, search, filter) with relevant properties
app/routes/home.tsx	4/5	CTA click tracking with location property
app/routes/login.tsx	4/5	User identification and login event capture
app/routes/profile.tsx	5/5	Proper logout tracking with reset() call for session cleanup
app/routes/signup.tsx	4/5	User identification, signup tracking, and exception capture in catch block
package.json	5/5	Correct PostHog dependencies added
react-router.config.ts	4/5	Enables v8_middleware for server-side tracking
vite.config.ts	3/5	SSR noExternal config correct; proxy only works in dev mode
posthog-setup-report.md	4/5	Comprehensive documentation of the integration
package-lock.json	5/5	Lock file updated correctly

---

App sanity check: 3/5 ⚠️

Criteria	Result	Description
App builds and runs	Uncertain	Invalid PostHog config option may cause runtime warnings/errors
Preserves existing env vars & configs	Yes	No existing configs modified destructively
No syntax or type errors	Yes	TypeScript types are correct
Correct imports/exports	Yes	All imports resolve correctly
Minimal, focused changes	Yes	Changes are focused on PostHog integration

Issues

• Invalid PostHog init option: The defaults: '2025-11-30' option in entry.client.tsx line 10 is not a valid PostHog configuration option. This may cause console warnings or unexpected behavior. Remove this line or replace with valid options like person_profiles: 'identified_only'. [CRITICAL]
• Hook usage in ErrorBoundary: Calling usePostHog() unconditionally at the start of ErrorBoundary in root.tsx (line 69) violates React's rules of hooks best practices for error boundaries. Consider using posthog.captureException() directly via the imported module instead. [MEDIUM]

Other completed criteria

• All imports use correct package names
• TypeScript types properly imported and used
• No hardcoded API keys in source code
• Existing app logic (auth, countries, etc.) preserved

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js ^1.324.1, posthog-node ^5.21.0, @posthog/react ^1.5.2
PostHog client initialized	Partial	Initialized in entry.client.tsx with invalid option; server middleware in posthog-middleware.ts
capture()	Yes	Multiple events captured across routes
identify()	Yes	Called on login and signup with username
Error tracking	Yes	captureException() in ErrorBoundary and signup catch block
Reverse proxy	Partial	Configured in Vite but only works during development

Issues

• Invalid init configuration: defaults: '2025-11-30' is not a recognized PostHog option. Remove or replace with valid configuration. [CRITICAL]
• Reverse proxy dev-only: The Vite server.proxy configuration only applies during vite dev. For production, you need a server-side proxy (e.g., in your hosting platform or a separate server config). Events will be blocked by adblockers in production. [MEDIUM]
• No automatic pageview tracking: Manual pageview capture is not implemented; relying on default PostHog autocapture which may not track SPA route changes correctly in React Router v7. Consider adding capture_pageview: true or manual pageview tracking on route changes. [LOW]

Other completed criteria

• PostHogProvider wraps the entire app
• Server-side middleware sets up PostHog context with session/distinct ID correlation
• Proper shutdown handling with posthog.shutdown()
• posthog.reset() called on logout
• No PII exposed in event properties (username/email are identifiers, not sensitive PII)
• __add_tracing_headers configured for distributed tracing

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
login.tsx	user_logged_in	Tracks successful logins with username
signup.tsx	user_signed_up, captureException	Tracks signups with username/email; captures signup errors
profile.tsx	user_logged_out	Tracks logouts with session reset
countries.tsx	country_claimed, country_liked, country_visited, country_search, country_filter_region	Core engagement events with country_name and region properties
home.tsx	explore_cta_clicked, learn_more_clicked	CTA engagement with location property
root.tsx	captureException	Global error boundary tracking

Issues

• Search event fires on every keystroke: The country_search event fires on every change when length > 2, which could result in high event volume. Consider debouncing. [LOW]

Other completed criteria

• Events represent real user actions (authentication, engagement, navigation)
• Events enriched with relevant properties (country_name, region, location)
• Conversion funnel trackable (signup → country interactions)
• Error tracking provides debugging visibility
• User identification enables cohort analysis

---

Reviewed by wizard workbench PR evaluator