[CI] (bd5a2b4) react-router/shopper

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: bd5a2b4
App: react-router/shopper
App directory: apps/react-router/shopper
Workbench branch: wizard-ci-bd5a2b4-react-router-shopper
Wizard branch: main
Examples branch: main
PostHog (MCP) branch: master
Timestamp: 2026-01-21T21:07:01.831Z
Duration: 321.1s

[wizard-ci-bot]

The files don't exist locally, but I have the complete diff provided in the PR description. I'll evaluate the PR based on the comprehensive diff information provided, which shows the full content of all changed files.

---

PR Evaluation Report

Summary

This PR adds PostHog analytics integration to a React Router v7 e-commerce application ("shopper"). It includes client-side SDK initialization via PostHogProvider, server-side middleware for session tracking, error boundary exception capture, and comprehensive custom event tracking across the shopping flow (product views, cart actions, checkout, search, and category filtering).

Files changed	Lines added	Lines removed
13	+768	-7

Confidence score: 4/5 👍

• Production proxy missing: The Vite server proxy for /ingest only works in development mode. Production deployments need a separate reverse proxy configuration (e.g., nginx, Vercel rewrites, or similar). [MEDIUM]
• Search event fires on every keystroke: product_searched event fires for every character typed (when term.length > 0), which will flood PostHog with events. Should debounce or fire on search submission. [MEDIUM]
• Missing user identification: No posthog.identify() calls when users authenticate or provide identifying information during checkout. [MEDIUM]

---

File changes

Filename	Score	Description
app/entry.client.tsx	4/5	Creates new client entry point with PostHog initialization using PostHogProvider. Uses env vars correctly. Has defaults and __add_tracing_headers options.
app/lib/posthog-middleware.ts	4/5	Server-side middleware using posthog-node with context-based API. Correctly extracts session/distinct IDs from headers and uses withContext.
app/root.tsx	4/5	Adds middleware export and error boundary exception capture via captureException.
app/routes/cart.tsx	5/5	Comprehensive cart event tracking: remove, quantity update, checkout started with rich properties.
app/routes/checkout.tsx	4/5	Tracks order_placed with order details. Could also identify user from form data.
app/routes/home.tsx	5/5	Clean CTA click tracking with location context.
app/routes/products..tsx	5/5	Add to cart tracking from product detail page with category and source properties.
app/routes/products.tsx	3/5	Search event fires on every keystroke which will generate excessive events. Category filter tracking is good.
package.json	5/5	Correctly adds @posthog/react, posthog-js, and posthog-node dependencies.
react-router.config.ts	5/5	Enables v8_middleware future flag required for middleware support.
vite.config.ts	4/5	Adds SSR noExternal config and dev server proxy. Production proxy needs separate solution.
package-lock.json	5/5	Lock file updated with new dependencies.
posthog-setup-report.md	5/5	Comprehensive documentation of integration.

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	Dependencies added correctly, no syntax errors visible
Preserves existing env vars & configs	Yes	Original vite.config.ts structure preserved with additions
No syntax or type errors	Yes	TypeScript types look correct, imports are valid
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

• New entry.client.tsx replaces default behavior: The diff shows this as a new file (+23/-0). If the app previously had a default entry client, this replaces it correctly with PostHog wrapping. However, if React Router was relying on its default entry client, this is the correct pattern. [LOW]

Other completed criteria

• Error handling preserved in ErrorBoundary
• Cart context and navigation logic unchanged
• Build configuration is valid with proper SSR noExternal settings
• Environment variables documented in setup report

---

PostHog implementation: 4/5 ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	@posthog/react, posthog-js, posthog-node all added to package.json
PostHog client initialized	Yes	Client-side: posthog.init() in entry.client.tsx with PostHogProvider. Server-side: new PostHog() in middleware with withContext
capture()	Yes	Multiple capture calls across routes for cart, checkout, search, and navigation events
identify()	No	No posthog.identify() calls present. Users are not identified even when providing checkout form data
Error tracking	Yes	captureException(error) in ErrorBoundary component
Reverse proxy	Partial	Dev server proxy configured in vite.config.ts, but production deployment needs separate configuration

Issues

• Missing user identification: No posthog.identify() calls when users provide their name/email during checkout. This means all events are anonymous and can't be tied to specific users. Should call posthog?.identify(email, { name: formData.fullName }) in the checkout flow. [MEDIUM]
• Dev-only reverse proxy: The Vite server proxy at /ingest only works during development. Production deployments will hit CORS/adblock issues unless a production reverse proxy is configured (e.g., Vercel rewrites, nginx config). The client initialization should also update api_host to use /ingest for the proxy to work. [MEDIUM]
• API host not using proxy: The api_host in entry.client.tsx is set to import.meta.env.VITE_PUBLIC_POSTHOG_HOST (direct PostHog URL) instead of /ingest which would leverage the reverse proxy. [MEDIUM]

Other completed criteria

• API key via environment variable (not hardcoded)
• PostHogProvider wraps application correctly
• Server middleware uses context-based API correctly
• Session and distinct ID headers passed from client to server
• Proper shutdown in middleware with .catch() for graceful handling

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
app/root.tsx	captureException	Captures errors from ErrorBoundary for exception monitoring
app/routes/home.tsx	cta_clicked	Tracks homepage CTA engagement with location context
app/routes/products.tsx	product_added_to_cart, product_searched, category_filtered	Tracks product listing interactions. Search event fires per keystroke (problematic).
app/routes/products..tsx	product_added_to_cart	Tracks add to cart from detail page with quantity and source
app/routes/cart.tsx	product_removed_from_cart, cart_quantity_updated, checkout_started	Comprehensive cart funnel tracking with item details
app/routes/checkout.tsx	order_placed	Tracks completed orders with total, tax, and item breakdown

Issues

• Search event over-firing: product_searched fires on every keystroke when term.length > 0. This will create excessive events and pollute analytics. Should debounce (300-500ms) or fire on form submission/blur. [MEDIUM]
• Missing product view event: No product_viewed event when users visit the product detail page. This is a key funnel metric. [LOW]
• Missing page view tracking: While PostHog auto-captures pageviews by default, explicit page tracking or capture_pageview config isn't mentioned. [LOW]

Other completed criteria

• Events represent real user actions (add to cart, checkout, order)
• Events include relevant properties (product_id, product_name, price, quantity)
• Source property distinguishes where actions originated (products_listing vs product_detail)
• Cart events include comprehensive item arrays for basket analysis
• Order events include subtotal, tax, and total for revenue tracking
• No PII in event properties (using product IDs, not raw user data)

---

Reviewed by wizard workbench PR evaluator