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

[wizard-ci-bot]

Automated wizard CI run

Trigger ID: d07456b
App: react-router/rrv7-starter
App directory: apps/react-router/rrv7-starter
Workbench branch: wizard-ci-d07456b-react-router-rrv7-starter
Wizard branch: main
Examples branch: test-ci
PostHog (MCP) branch: master
Timestamp: 2026-01-14T19:32:58.133Z
Duration: 356.0s

[wizard-ci-bot]

Now I have a complete picture. Let me write the evaluation report.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router v7 application (CloutHub - a satirical fake influencer social network). The integration includes client-side initialization via PostHogProvider, server-side middleware for session correlation, custom event tracking across multiple components, and error boundary exception capture. However, the PR contains debug comments scattered throughout multiple files and has notable issues with PostHog initialization configuration.

Files changed	Lines added	Lines removed
21	+632	-153

Confidence score: 3/5 🤔

• Debug comments pollution: Every modified file contains // QUACK QUACK IM A BIG FLUFFY DOG comment at the top, which is unprofessional and should be removed before merging [CRITICAL]
• PostHog initialization uses invalid config option: defaults: '2025-11-30' is not a valid PostHog config option - this should likely be defaultIdentifiedOnly or removed [MEDIUM]
• No reverse proxy configured: PostHog events will be blocked by ad blockers since requests go directly to us.i.posthog.com [MEDIUM]
• Missing pageview tracking: No automatic pageview capture is configured - relies entirely on manual event tracking [MEDIUM]

---

File changes

Filename	Score	Description
app/entry.client.tsx	3/5	New client entry point with PostHog initialization. Uses invalid defaults config option. Contains debug comment.
app/lib/posthog-middleware.ts	4/5	Server-side middleware for session/user correlation. Well-structured but contains debug comment.
app/root.tsx	3/5	Adds middleware export and error tracking via captureException. Contains debug comment.
app/components/PostCard.tsx	4/5	Adds like/unlike event tracking with good properties. Contains debug comment and formatting changes.
app/components/header.tsx	4/5	Adds navigation and CTA click tracking. Contains debug comment and formatting changes.
app/routes/buy-followers.tsx	4/5	Adds package selection and purchase conversion events. Contains debug comment and formatting changes.
app/routes/home.tsx	4/5	Adds CTA click tracking. Contains debug comment and formatting changes.
app/routes/profile.tsx	4/5	Adds user follow event tracking. Contains debug comment and formatting changes.
app/routes/analytics.tsx	5/5	Formatting changes only, no PostHog integration. Clean.
app/routes/feed.tsx	5/5	Formatting changes only, no PostHog integration. Clean.
package.json	5/5	Correctly adds @posthog/react, posthog-js, and posthog-node dependencies.
vite.config.ts	4/5	Adds PostHog packages to SSR noExternal. Contains debug comment.
react-router.config.ts	4/5	Enables v8_middleware future flag. Contains debug comment.
.env.example	5/5	Documents required PostHog environment variables.
env.d.ts	4/5	Adds TypeScript declarations for PostHog env vars. Contains debug comment.
app/components/StatCard.tsx	5/5	Formatting changes only. Clean.
app/hooks/use-hydrated.ts	5/5	Formatting changes only (semicolons). Clean.
app/lib/data/fake-data.ts	5/5	Formatting changes only. Clean.
app/lib/utils/localStorage.ts	5/5	Formatting changes only. Clean.
pnpm-lock.yaml	5/5	Lock file updates for new dependencies.
posthog-setup-report.md	5/5	Good documentation of the integration.

---

App sanity check: 3/5 ⚠️

Criteria	Result	Description
App builds and runs	Likely	Dependencies correct, imports valid, but defaults: '2025-11-30' may cause runtime warning
Preserves existing env vars & configs	Yes	Original VITE_SITE_URL preserved, PostHog vars added
No syntax or type errors	Yes	TypeScript declarations added, imports correct
Correct imports/exports	Yes	@posthog/react and posthog-js imports correct
Minimal, focused changes	No	Extensive formatting/whitespace changes mixed with functional changes

Issues

• Debug comments in production code: 10+ files contain // QUACK QUACK IM A BIG FLUFFY DOG debug comment that must be removed before merging [CRITICAL]
• Mixed changes: Formatting/whitespace changes (removing trailing newlines, collapsing JSX) are mixed with PostHog integration changes, making review difficult [MEDIUM]
• Invalid PostHog config: defaults: '2025-11-30' in entry.client.tsx is not a valid PostHog option [MEDIUM]

Other completed criteria

• Environment variables properly documented in .env.example
• TypeScript declarations added for new env vars
• SSR compatibility handled via noExternal in vite config
• Middleware future flag enabled correctly

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.321.2, posthog-node@^5.21.0, @posthog/react@^1.5.2
PostHog client initialized	Partial	Client init in entry.client.tsx, but uses invalid defaults option
capture()	Yes	Multiple capture calls across components with good properties
identify()	No	No user identification implemented
Error tracking	Yes	captureException(error) in ErrorBoundary
Reverse proxy	No	Direct calls to us.i.posthog.com - will be blocked by ad blockers

Issues

• No reverse proxy: Events sent directly to PostHog API host will be blocked by ad blockers. Should configure a /ingest proxy endpoint [MEDIUM]
• No pageview tracking: Neither capture_pageview: true nor manual `` events are configured - navigation won't be tracked [MEDIUM]
• No user identification: posthog.identify() is never called despite the app having a fake user concept [LOW]
• Invalid config option: defaults: '2025-11-30' is not a valid PostHog configuration option [MEDIUM]

Other completed criteria

• Server-side middleware correctly correlates sessions via headers
• __add_tracing_headers configured for localhost
• PostHog provider wraps the entire app
• Proper shutdown handling in middleware
• No PII in event properties

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
app/routes/buy-followers.tsx	follower_package_selected, follower_package_purchased	Key conversion funnel events with rich properties (price, package details, followers count)
app/components/PostCard.tsx	post_liked, post_unliked	Engagement tracking with post context (id, username, verified status)
app/components/header.tsx	navigation_link_clicked, buy_followers_cta_clicked	Navigation and CTA tracking with source/destination
app/routes/home.tsx	cta_clicked	Homepage CTA tracking with button name and destination
app/routes/profile.tsx	user_followed	Social interaction tracking with followed username
app/root.tsx	captureException	Error boundary exception capture

Issues

• Missing Analytics page events: The analytics dashboard has no PostHog events despite being a key page [LOW]
• No Feed page events: The feed page relies only on PostCard events, no page-level tracking [LOW]

Other completed criteria

• Events represent real user actions and product flows
• Purchase funnel events enable conversion analysis
• Rich event properties enable breakdown analysis
• Error tracking captures application errors
• Events follow consistent naming convention (snake_case)
• Properties include contextual information (source, current state)

---

Reviewed by wizard workbench PR evaluator