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

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: afd8cc2
App: react-router/react-router-v7-project
App directory: apps/react-router/react-router-v7-project
Workbench branch: wizard-ci-afd8cc2-react-router-react-router-v7-project
Wizard branch: main
Examples branch: main
PostHog (MCP) branch: master
Timestamp: 2026-01-16T14:00:22.569Z
Duration: 359.1s

[wizard-ci-bot]

Now I have all the information needed to provide a comprehensive PR evaluation. Let me compile my findings.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router v7 framework application. The implementation includes client-side SDK initialization, server-side middleware for context propagation, user identification on auth events, error tracking via error boundary, and custom event tracking across key user flows (country exploration, search/filter, and authentication).

Files changed	Lines added	Lines removed
14	+740	-24

Confidence score: 3/5 🤔

• Invalid defaults option in PostHog init: The defaults: '2025-11-30' option in entry.client.tsx is not a valid PostHog configuration option. This will be silently ignored but indicates a misunderstanding of the API. [MEDIUM]
• Missing automatic pageview tracking: The PostHog init does not enable capture_pageview: true or set up route change listeners. The setup report claims "automatic pageview tracking" but this is not configured. [MEDIUM]
• Server-side middleware creates PostHog client on every request: The middleware instantiates a new PostHog instance for each request with flushAt: 1 and flushInterval: 0, which is inefficient. Consider singleton pattern or connection pooling. [MEDIUM]
• No reverse proxy configured: Events are sent directly to us.i.posthog.com, making them susceptible to ad blockers. No proxy configuration is present. [MEDIUM]

---

File changes

Filename	Score	Description
app/entry.client.tsx	3/5	PostHog init with invalid defaults option; adds PostHogProvider wrapper correctly
app/lib/posthog-middleware.ts	3/5	New middleware for server-side context; creates client per-request which is inefficient
app/root.tsx	4/5	Properly registers middleware and adds error boundary exception capture
app/routes/countries.tsx	4/5	Good event tracking for user actions (search, filter, claim, like, visit) with properties
app/routes/country.tsx	4/5	Tracks country views with useRef to prevent double-firing in StrictMode
app/routes/home.tsx	3/5	Replaced <Link> with <button> for tracking - changes navigation semantics unnecessarily
app/routes/login.tsx	4/5	Proper identify and capture on login
app/routes/profile.tsx	5/5	Clean logout tracking with posthog.reset()
app/routes/signup.tsx	4/5	Proper identify and capture on signup; includes exception capture in catch block
package.json	5/5	Correctly adds @posthog/react, posthog-js, and posthog-node
react-router.config.ts	4/5	Enables v8_middleware future flag required for middleware
vite.config.ts	4/5	Adds SSR noExternal for PostHog packages to prevent bundling issues
posthog-setup-report.md	3/5	New documentation; claims "automatic pageview tracking" which is not configured
package-lock.json	5/5	Lock file updated with PostHog dependencies

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	Dependencies installed correctly, config files valid
Preserves existing env vars & configs	Yes	Only adds new config; SSR and existing settings preserved
No syntax or type errors	Yes	All TypeScript types appear correct
Correct imports/exports	Yes	All imports from @posthog/react, posthog-js, posthog-node are correct
Minimal, focused changes	Yes	Changes are focused on PostHog integration only

Issues

• home.tsx Link→button conversion: The "Explore Now" <Link> was replaced with a <button> using useNavigate(). This works but changes accessibility semantics and removes the ability to right-click/open in new tab. Could have used the <Link> with an onClick handler instead. [LOW]

Other completed criteria

• Environment variables documented in posthog-setup-report.md
• Build configuration for SSR is valid
• Appropriate error handling in clientLoader functions preserved
• Optional chaining used throughout (posthog?.capture()) for safety

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js: ^1.325.0, posthog-node: ^5.21.0, @posthog/react: ^1.5.2
PostHog client initialized	Yes	Init in entry.client.tsx with API key and host from env vars
capture()	Yes	10 custom events tracked across routes
identify()	Yes	Users identified on login and signup with id, username, email
Error tracking	Yes	captureException() in ErrorBoundary and signup catch block
Reverse proxy	No	Events sent directly to us.i.posthog.com - no proxy configured

Issues

• Invalid defaults configuration: defaults: '2025-11-30' in posthog.init() is not a valid option. This appears to be a confused attempt at setting API version or defaults. [MEDIUM]
• No automatic pageview tracking: Despite the setup report claiming automatic pageview tracking, capture_pageview is not set to true and no route change listener is configured. React Router v7 apps need explicit pageview tracking on navigation. [MEDIUM]
• No reverse proxy: Events go directly to PostHog, making them vulnerable to ad blockers. A proxy route should be configured. [MEDIUM]
• Per-request PostHog instantiation: The middleware creates a new PostHog(posthog-node) instance for every server request. This is inefficient and should use a singleton pattern. [MEDIUM]
• __add_tracing_headers is internal API: Using __add_tracing_headers relies on an internal/undocumented API that could change. [LOW]

Other completed criteria

• PostHogProvider correctly wraps the app
• Server-side middleware properly propagates session/distinct ID headers
• posthog.reset() called on logout to clear user identity
• Proper cleanup with posthog.shutdown() in middleware
• SSR noExternal config prevents bundling issues
• No PII in event properties (username/email in identify is appropriate)

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
signup.tsx	user_signed_up, identify(), captureException	Tracks new user registration with user properties
login.tsx	user_logged_in, identify()	Tracks login with user identification
profile.tsx	user_logged_out, reset()	Tracks logout and clears user identity
countries.tsx	countries_searched, countries_filtered, country_claimed, country_liked, country_visited	Comprehensive tracking of list interactions with relevant properties
country.tsx	country_viewed	Tracks detail page views with country metadata
home.tsx	explore_clicked	Tracks CTA engagement with location property
root.tsx	captureException	Global error boundary tracking

Issues

• Missing pageview events: No `` events captured, limiting funnel and path analysis. [MEDIUM]
• Search tracking on blur only: countries_searched fires on blur, missing searches where users don't blur (e.g., navigate away). Consider also tracking on navigation or form submission. [LOW]

Other completed criteria

• Events have meaningful properties (country_name, region, population, search_term, results_count)
• Events enable funnel analysis (explore_clicked → user_signed_up → country_claimed)
• Events capture real user intent and product engagement
• User identification links events to real users
• Error tracking provides exception visibility

---

Reviewed by wizard workbench PR evaluator