[CI] (a283762) react-router/rrv7-starter

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: a283762
App: react-router/rrv7-starter
App directory: apps/react-router/rrv7-starter
Workbench branch: wizard-ci-a283762-react-router-rrv7-starter
Wizard branch: main
Examples branch: main
PostHog (MCP) branch: master
Timestamp: 2026-01-15T22:36:35.214Z
Duration: 280.0s

[wizard-ci-bot]

Now I have all the information I need to write the evaluation report. Let me compile my findings:

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router v7 "fake social network" demo app. It adds client-side PostHog initialization via a new entry.client.tsx, implements event tracking across key user interactions (likes, follows, CTA clicks, purchase flows), adds error boundary exception capture, and includes appropriate code formatting changes. The integration follows recommended patterns but has some notable gaps.

Files changed	Lines added	Lines removed
17	+557	-139

Confidence score: 3/5 🤔

• Missing reverse proxy configuration: No reverse proxy setup to circumvent adblockers blocking PostHog requests. This can significantly impact data collection in production. [MEDIUM]
• Missing user identification: No posthog.identify() implementation despite the app having user context. While this is a fake app, the pattern should be demonstrated. [MEDIUM]
• Environment variables not documented in .env.example: The PostHog env vars (VITE_PUBLIC_POSTHOG_KEY, VITE_PUBLIC_POSTHOG_HOST) are in .env but not in .env.example, which only has VITE_SITE_URL. This breaks the onboarding experience for new developers. [CRITICAL]
• Pageview tracking not explicitly configured: No explicit capture_pageview configuration in init; relying on defaults may cause issues in SPA routing. [MEDIUM]

---

File changes

Filename	Score	Description
app/entry.client.tsx	4/5	New file. Properly initializes PostHog with PostHogProvider wrapping the app. Uses defaults: '2025-11-30' and tracing headers. Missing explicit autocapture/pageview config.
app/root.tsx	4/5	Adds usePostHog and captureException(error) in ErrorBoundary. Correctly captures errors for PostHog monitoring.
app/components/PostCard.tsx	5/5	Adds like/unlike event tracking with relevant properties (post_id, username, verified). Clean implementation.
app/components/header.tsx	4/5	Tracks header "Buy Followers" button click with current follower count. Good funnel tracking start.
app/components/StatCard.tsx	5/5	Formatting changes only - no functional changes.
app/routes/buy-followers.tsx	5/5	Comprehensive tracking: package selection and purchase completion with full properties (amount, bonus, price, total). Well-designed conversion funnel.
app/routes/home.tsx	4/5	Tracks CTA clicks with cta_name and page properties. Good for understanding user intent.
app/routes/profile.tsx	4/5	Tracks user follows. Note: only tracks follow, not unfollow - asymmetric tracking.
app/routes/analytics.tsx	5/5	Formatting changes only - no PostHog additions needed for this display-only page.
app/routes/feed.tsx	5/5	Formatting changes only. Feed page uses PostCard which handles tracking.
app/hooks/use-hydrated.ts	5/5	Formatting/linting changes only (semicolons removed).
app/lib/data/fake-data.ts	5/5	Formatting changes only (quote style, trailing newline).
app/lib/utils/localStorage.ts	5/5	Formatting changes only (whitespace).
package.json	5/5	Correctly adds posthog-js, posthog-node, @posthog/react dependencies.
pnpm-lock.yaml	5/5	Lock file updated correctly with PostHog dependencies and transitive deps.
vite.config.ts	5/5	Correctly adds posthog-js and @posthog/react to SSR noExternal for dev builds.
posthog-setup-report.md	4/5	Helpful documentation of implemented events. References .env file that exists but doesn't document required env vars in .env.example.

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	Dependencies added correctly, SSR config updated, no build-breaking issues
Preserves existing env vars & configs	Partial	Original .env.example unchanged; PostHog env vars added to .env but not documented in example
No syntax or type errors	Yes	All TypeScript code is valid, hooks used correctly
Correct imports/exports	Yes	@posthog/react and posthog-js imported correctly throughout
Minimal, focused changes	Partial	Many formatting/whitespace changes mixed with functional changes

Issues

• Environment variables not in .env.example: VITE_PUBLIC_POSTHOG_KEY and VITE_PUBLIC_POSTHOG_HOST are required but only documented in .env, not .env.example. New developers cloning the repo won't know these are needed. Add them to .env.example with placeholder values. [CRITICAL]
• Excessive formatting changes: Many files have formatting-only changes (StatCard, analytics, feed, etc.) mixed with functional PostHog changes. While not breaking, this adds noise to the diff and makes review harder. [LOW]

Other completed criteria

• PostHog SDK packages installed correctly in dependencies
• Vite SSR noExternal configuration updated properly
• TypeScript types handled correctly via @posthog/react hooks
• No hardcoded API keys in source code (uses environment variables)
• Existing app functionality preserved (localStorage, routing, animations)

---

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 in package.json
PostHog client initialized	Yes	Initialized in entry.client.tsx with PostHogProvider wrapping the app, uses env vars for API key/host
capture()	Yes	7 distinct events tracked across components (like, unlike, follow, package selection, purchase, CTA clicks)
identify()	No	No user identification implemented despite app having user context (fakeUser)
Error tracking	Yes	captureException(error) in ErrorBoundary captures route errors
Reverse proxy	No	No reverse proxy configured; events may be blocked by adblockers

Issues

• Missing reverse proxy: No reverse proxy configuration to avoid adblocker interference. PostHog documentation recommends setting up a reverse proxy for production apps. This can cause significant data loss. [MEDIUM]
• Missing posthog.identify(): The app has a fakeUser context but never calls posthog.identify(). While this is a demo app, the pattern should be demonstrated to show proper user identification practices. [MEDIUM]
• Implicit pageview tracking: No explicit capture_pageview setting in init options. The React Router SPA may not track page navigation correctly with default settings. Should explicitly configure capture_pageview: false and use router hooks, or verify the defaults work with React Router. [MEDIUM]
• posthog-node installed but unused: The posthog-node package is in dependencies but not used anywhere. This is server-side SDK bloat. [LOW]

Other completed criteria

• PostHogProvider correctly wraps app in entry.client.tsx
• Optional chaining (posthog?.capture()) used throughout for safety
• API host configuration via environment variable
• Uses modern defaults: '2025-11-30' configuration
• Tracing headers configured for localhost and current host
• No PII in captured event properties

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
app/components/PostCard.tsx	post_liked, post_unliked	Engagement tracking with post_id, username, verified status. Enables likes analysis and engagement metrics.
app/components/header.tsx	buy_followers_header_clicked	Top-of-funnel tracking with current_followers. Good for conversion funnel analysis.
app/routes/buy-followers.tsx	follower_package_selected, follower_purchase_completed	Full purchase funnel with package details (amount, bonus, price, total). Enables revenue and conversion analysis.
app/routes/home.tsx	cta_clicked	CTA engagement with cta_name property. Enables A/B testing and landing page optimization.
app/routes/profile.tsx	user_followed	Social engagement with followed_username. Enables network growth analysis.
app/root.tsx	captureException	Error boundary captures exceptions for debugging and reliability monitoring.

Issues

• Asymmetric follow tracking: user_followed is tracked but user_unfollowed is not, creating incomplete engagement data. [LOW]
• No page view tracking verified: Without explicit pageview configuration, navigation between routes may not be properly captured. [MEDIUM]

Other completed criteria

• Events capture real user actions (likes, purchases, follows, clicks)
• Events are enriched with relevant properties for segmentation
• Conversion funnel is properly instrumented (header click → package selection → purchase)
• Error tracking provides debugging value
• Event naming follows snake_case convention consistently
• No PII captured in properties

---

Reviewed by wizard workbench PR evaluator