[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 963eeb8
App: react-router/react-router-v7-project
App directory: apps/react-router/react-router-v7-project
Workbench branch: wizard-ci-963eeb8-react-router-react-router-v7-project
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-09-03T18:33:13.001Z
Duration: 395.7s

YARA Scanner

✓ 185 tool calls scanned, 0 violations detected

No violations: ✓ 185 clean scans

[wizard-ci-bot]

Now I have enough context to produce the evaluation.

---

PR Evaluation Report

Summary

This PR integrates PostHog into a React Router v7 framework mode app. It adds posthog-js initialized in a client-side module (posthog.client.ts) imported via entry.client.tsx, with user identification in the auth context, custom event captures across routes, and automatic exception capture via config. The integration uses dynamic imports throughout instead of the recommended PostHogProvider pattern.

Files changed	Lines added	Lines removed
9	+127	-18

Confidence score: 5/5 🧙

• No reverse proxy configured: The integration does not set up a reverse proxy (e.g., via Vite rewrites or React Router middleware), which means client-side events are likely to be blocked by ad blockers. [MEDIUM]
• ErrorBoundary not wired to PostHog: The existing ErrorBoundary in root.tsx was not updated with posthog.captureException(error). React errors caught by error boundaries do NOT propagate to window.onerror, so capture_unhandled_errors: true will not capture React rendering errors. [MEDIUM]
• Outdated defaults value: Uses "2026-01-30" instead of the latest "2026-05-30" from the docs. [LOW]

---

File changes

Filename	Score	Description
app/lib/posthog.client.ts	4/5	New PostHog init module with env var validation, error tracking config. Uses older defaults value.
app/entry.client.tsx	4/5	Side-effect import of PostHog module — works but doesn't use PostHogProvider.
app/context/AuthContext.tsx	5/5	Well-implemented identify/reset lifecycle using user.id as distinct_id, person properties for email/username, reset on logout.
app/routes/countries.tsx	4/5	Custom events for country actions with enriched properties (country_code, region).
app/routes/login.tsx	4/5	Captures user_logged_in event on successful login.
app/routes/signup.tsx	4/5	Captures user_signed_up event on successful signup.
app/routes/profile.tsx	4/5	Captures user_logged_out event before logout.
.env.example	5/5	Documents both required env vars.
package.json	5/5	Adds posthog-js dependency.

---

App sanity check ✅

Criteria	Result	Description
App builds and runs	Yes	No syntax errors, valid imports, side-effect import pattern is safe
Preserves existing env vars & configs	Yes	No existing configs modified, only additions
No syntax or type errors	Yes	All code is syntactically valid TypeScript/TSX
Correct imports/exports	Yes	posthog-js imported correctly, ~/lib/posthog.client path alias resolves
Minimal, focused changes	Yes	All changes relate to PostHog integration
Pre-existing issues	None	Base app is functional

Issues

No issues.

Other completed criteria

• Environment variables documented in .env.example
• Build configuration unchanged and valid
• Existing app functionality preserved (auth flow, country interactions)

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.425.1 added to package.json
PostHog client initialized	Yes	Initialized in posthog.client.ts with env vars, imported as side-effect in entry.client.tsx
capture()	Yes	6 meaningful capture calls across routes
identify()	Yes	user.id used as distinct_id with email/username as person properties; reset on logout
Error tracking	Yes	capture_exceptions configured with capture_unhandled_errors: true and capture_unhandled_rejections: true
Reverse proxy	No	Not configured — no Vite rewrites or middleware proxy set up

Issues

• ErrorBoundary not wired to PostHog: The existing ErrorBoundary in root.tsx already handles route errors but does not call posthog.captureException(error). React errors caught by error boundaries do NOT bubble to window.onerror, so the capture_unhandled_errors config cannot catch them. Per the React Router v7 framework mode docs, the ErrorBoundary should call captureException. [MEDIUM]
• No reverse proxy: Client-side events sent directly to us.i.posthog.com will be blocked by ad blockers. The docs recommend setting up a reverse proxy via Next.js/Vite rewrites or a managed proxy. [MEDIUM]
• Outdated defaults value: defaults: "2026-01-30" should be "2026-05-30" per current docs. [LOW]
• No PostHogProvider: The docs for React Router v7 framework mode recommend wrapping the app with PostHogProvider from @posthog/react and using the usePostHog hook. The PR instead uses repetitive dynamic imports (void import('~/lib/posthog.client').then(...)) throughout. This works but is unconventional and verbose. [LOW]

Other completed criteria

• API key loaded from VITE_PUBLIC_POSTHOG_PROJECT_TOKEN environment variable
• Host loaded from VITE_PUBLIC_POSTHOG_HOST environment variable
• Good dev-time error messages when env vars are missing
• posthog.reset() called on logout
• posthog.identify() called on login, signup, and page load when user exists
• Proper handling of storage sync for multi-tab identity

---

PostHog insights and events ✅

Filename	PostHog events	Description
app/routes/login.tsx	user_logged_in	Captures successful login action
app/routes/signup.tsx	user_signed_up	Captures successful signup action
app/routes/profile.tsx	user_logged_out	Captures logout action
app/routes/countries.tsx	country_claimed, country_liked, country_visited	Captures country interaction actions with country_code and region properties; only fires on first interaction (not toggles)
app/context/AuthContext.tsx	identify, reset	Identifies users with user.id as distinct_id, sets email/username as person properties

Issues

No issues.

Other completed criteria

• Events represent real user actions (login, signup, logout, country interactions)
• Events enable product insights (login → country interaction funnel, engagement tracking)
• Country events enriched with country_code and region properties
• No PII in capture properties — email/username correctly placed in identify person properties
• Consistent snake_case naming convention across all events

---

Reviewed by wizard workbench PR evaluator