[CI] (6fb03e7) react-router/rrv7-starter

[wizard-ci-bot]

Automated wizard CI run

Source: scheduled
Trigger ID: 6fb03e7
App: react-router/rrv7-starter
App directory: apps/react-router/rrv7-starter
Workbench branch: wizard-ci-6fb03e7-react-router-rrv7-starter
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-05-13T17:38:11.215Z
Duration: 420.8s

[wizard-ci-bot]

Now I have all the context needed. Let me produce the evaluation.

---

PR Evaluation Report

Summary

This PR integrates PostHog into a React Router v7 framework mode (SSR) app called "CloutHub." It adds client-side initialization via entry.client.tsx with PostHogProvider, server-side middleware using posthog-node, error tracking via captureException in the ErrorBoundary, and six custom capture events across multiple routes. The PR also includes significant cosmetic reformatting.

Files changed	Lines added	Lines removed
19	+185	-132

Confidence score: 4/5 👍

• feed_viewed captured in useEffect: The feed_viewed event is captured inside a useEffect with [posthog] dependency. Per React rules, analytics in useEffect reacting to state/context changes is discouraged — this event will also fire on every re-render where posthog reference changes. It should use [] as dependency or be handled differently. [MEDIUM]
• No identify() call anywhere: There is no posthog.identify() call in the app. For a client-side app, user identification is a recommended core requirement. No posthog.reset() on logout either. [CRITICAL]
• No reverse proxy configured: The app does not configure a reverse proxy (e.g., via Vite rewrites or React Router rewrites) for client-side PostHog requests. This is recommended for client-side apps to avoid ad blocker interception. [MEDIUM]
• Gratuitous reformatting across many files: Many files have cosmetic-only changes (whitespace, line wrapping, semicolons) that are unrelated to PostHog integration, increasing diff noise. [LOW]
• .env.example not updated: The .env.example file was not updated with the new PostHog env vars (VITE_PUBLIC_POSTHOG_PROJECT_TOKEN, VITE_PUBLIC_POSTHOG_HOST), only .env was modified (which is not committed). [MEDIUM]

---

File changes

Filename	Score	Description
app/entry.client.tsx	5/5	New file: initializes posthog-js with env vars, wraps app in PostHogProvider with tracing headers — matches docs exactly
app/lib/posthog-middleware.ts	5/5	New file: server-side PostHog middleware with context-based session/distinct ID correlation, proper shutdown
app/root.tsx	4/5	Exports middleware array, adds ErrorBoundary exception capture. captureException called during render (not in effect) but acceptable for error boundaries
app/routes/buy-followers.tsx	5/5	Adds follower_package_selected and followers_purchased capture in event handlers with rich properties
app/components/PostCard.tsx	5/5	Adds post_liked/post_unliked capture in click handler with relevant properties
app/routes/profile.tsx	4/5	Adds follower_followed_back capture in click handler
app/routes/feed.tsx	3/5	feed_viewed in useEffect with [posthog] dep — may double-fire
package.json	5/5	Adds posthog-js, @posthog/react, posthog-node
react-router.config.ts	5/5	Enables v8_middleware future flag
vite.config.ts	5/5	Adds posthog-js and @posthog/react to ssr.noExternal
env.d.ts	5/5	TypeScript declarations for new env vars
Other files	3/5	Cosmetic reformatting only (header, StatCard, home, analytics, localStorage, etc.)

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	All changes are syntactically valid, dependencies added, config correct
Preserves existing env vars & configs	Yes	Existing configs augmented, not replaced
No syntax or type errors	Yes	TypeScript declarations added for new env vars, imports correct
Correct imports/exports	Yes	posthog-js, @posthog/react, posthog-node all correctly imported in appropriate contexts
Minimal, focused changes	No	Significant cosmetic reformatting across 10+ files unrelated to PostHog
Pre-existing issues	None	No pre-existing issues identified

Issues

• Gratuitous reformatting: Many files (header.tsx, StatCard.tsx, home.tsx, analytics.tsx, localStorage.ts, etc.) have whitespace/formatting changes unrelated to PostHog integration. This adds noise to the diff. [LOW]
• .env.example not updated: The .env.example file still only contains VITE_SITE_URL. The new PostHog env vars should be documented there for other developers. [MEDIUM]

Other completed criteria

• App builds without errors — all dependencies and configs are valid
• Preserves all existing app functionality and env vars
• No syntax or type errors introduced
• All imports resolve correctly
• Build configuration (vite.config.ts, react-router.config.ts) is valid

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js, @posthog/react, posthog-node added to package.json
PostHog client initialized	Yes	Client: posthog.init() in entry.client.tsx with env vars and defaults. Server: posthog-node in middleware with flushAt: 1, flushInterval: 0
capture()	Yes	Six meaningful capture calls across buy-followers, PostCard, feed, profile
identify()	No	No posthog.identify() call anywhere in the app. No posthog.reset() either.
Error tracking	Yes	posthog.captureException(error) in root ErrorBoundary
Reverse proxy	No	No reverse proxy configured for client-side requests

Issues

• No user identification: The app has no posthog.identify() call. All events will be associated with anonymous IDs only. For a client-side app, identification is critical for linking user sessions and building user-level insights. [CRITICAL]
• No reverse proxy: No reverse proxy is configured. Client-side PostHog requests go directly to us.i.posthog.com and may be blocked by ad blockers. A Vite proxy or React Router rewrite should be added. [MEDIUM]

Other completed criteria

• PostHog SDK correctly added to dependencies with recent versions
• Client initialized with api_host from env var, defaults set, tracing headers enabled
• Server middleware correctly uses withContext() for session correlation
• API key loaded from environment variables (not hardcoded)
• API host correctly configured to https://us.i.posthog.com
• Error tracking via captureException in ErrorBoundary

---

PostHog insights and events ⚠️

Filename	PostHog events	Description
app/routes/feed.tsx	feed_viewed	Captures feed page view with post count — top of funnel
app/routes/buy-followers.tsx	follower_package_selected, followers_purchased	Captures package selection and purchase completion with price, amount, bonus properties
app/components/PostCard.tsx	post_liked, post_unliked	Captures like/unlike actions with post ID and username
app/routes/profile.tsx	follower_followed_back	Captures follow-back action with username
app/root.tsx	captureException	Captures unhandled errors in ErrorBoundary

Issues

• feed_viewed may double-fire: The feed_viewed event uses useEffect with [posthog] dependency. If the posthog reference from usePostHog() changes (e.g., re-renders), this will fire multiple times. Should use [] or a ref guard. [MEDIUM]

Other completed criteria

• Events represent real user actions (liking, purchasing, selecting packages, viewing feed)
• Events enable product insights — can build purchase funnel (feed_viewed → package_selected → purchased)
• Events include relevant properties (post_id, price, amount, bonus, package_index)
• No PII in event properties — only post IDs, usernames (app handles), and numeric values
• Event names are descriptive and use consistent snake_case convention

---

Reviewed by wizard workbench PR evaluator