[CI] (3f39e0e) react-router/shopper

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 3f39e0e
App: react-router/shopper
App directory: apps/react-router/shopper
Workbench branch: wizard-ci-3f39e0e-react-router-shopper
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-09-23T22:19:18.485Z
Duration: 383.3s

YARA Scanner

✓ 164 tool calls scanned, 0 violations detected

No violations: ✓ 164 clean scans

[wizard-ci-bot]

Now I have enough context. Let me produce the evaluation.

---

PR Evaluation Report

Summary

This PR integrates PostHog into a React Router v7 framework mode shopping app. It adds posthog-js and @posthog/react, initializes PostHog in entry.client.tsx with PostHogProvider and PostHogErrorBoundary, and instruments several e-commerce events across cart, checkout, and product routes. However, it has critical gaps: the required vite.config.ts SSR configuration is missing, a likely-hallucinated posthog.logger API is used, and user identification is absent.

Files changed	Lines added	Lines removed
7	+118	-0

Confidence score: 3/5 🤔

• Missing ssr.noExternal in vite.config.ts: React Router v7 framework mode docs explicitly require ssr: { noExternal: ['posthog-js', '@posthog/react'] } to avoid SSR errors. This is missing and will likely break the build or cause server-side rendering failures. [CRITICAL]
• posthog.logger is not a documented SDK API: The checkout route uses posthog.logger.info(...), but the posthog-js SDK reference documents posthog.captureLog() — not a .logger property. This is likely a hallucinated API that will throw a runtime error on the checkout page. [CRITICAL]
• No identify() implementation: This is a shopper app with a checkout form collecting name and email, yet no posthog.identify() call is made anywhere, meaning all events remain anonymous. [MEDIUM]
• No reverse proxy configured: No proxy rewrites set up for client-side PostHog requests, leaving events vulnerable to ad blockers. [MEDIUM]

---

File changes

Filename	Score	Description
apps/.../shopper/.env.example	4/5	Adds VITE_PUBLIC_POSTHOG_PROJECT_TOKEN and VITE_PUBLIC_POSTHOG_HOST
apps/.../shopper/app/entry.client.tsx	4/5	PostHog init with provider, error boundary, env var validation, and defaults option
apps/.../shopper/app/routes/cart.tsx	4/5	Adds capture events for cart item removal, quantity update, and checkout start
apps/.../shopper/app/routes/checkout.tsx	1/5	Uses undocumented posthog.logger API; otherwise good order_completed event
apps/.../shopper/app/routes/products..tsx	4/5	Captures product_added with enriched properties
apps/.../shopper/app/routes/products.tsx	4/5	Captures product_added and product_category_selected events
apps/.../shopper/package.json	5/5	Correctly adds posthog-js and @posthog/react

---

App sanity check ❌

Criteria	Result	Description
App builds and runs	No	Missing ssr.noExternal config in vite.config.ts will cause SSR bundling errors for posthog-js and @posthog/react
Preserves existing env vars & configs	Yes	Existing code and configs are untouched
No syntax or type errors	No	posthog.logger is not a documented posthog-js API; accessing .logger.info() will likely throw at runtime
Correct imports/exports	Yes	All imports from posthog-js and @posthog/react are valid
Minimal, focused changes	Yes	All changes are PostHog-related, no scope creep
Pre-existing issues	None	Base app appears clean

Issues

• Missing ssr.noExternal in vite.config.ts: The PostHog docs for React Router v7 framework mode explicitly require adding ssr: { noExternal: ['posthog-js', '@posthog/react'] } to the Vite config. Without this, SSR will attempt to externalize these packages and fail. Add the ssr block to vite.config.ts. [CRITICAL]
• Undocumented posthog.logger API: In checkout.tsx, const checkoutLogger = posthog.logger is used and then checkoutLogger.info(...) is called. The posthog-js SDK reference documents posthog.captureLog({ body, level, attributes }) but not a .logger property with .info() method. Replace with posthog.captureLog({ body: "checkout submitted", level: "info", attributes: {...} }). [CRITICAL]
• Missing optional chaining on posthog calls: The docs recommend posthog?.capture() to handle cases where PostHog is not yet initialized. All route files use posthog.capture() without optional chaining. [LOW]

Other completed criteria

• Environment variables documented in .env.example
• Existing app code and configs preserved
• Changes are minimal and focused on PostHog integration
• Package.json correctly updated with dependencies

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js ^1.434.12 and @posthog/react ^1.11.1 added to package.json
PostHog client initialized	Yes	posthog.init() called in entry.client.tsx with env vars and defaults: "2026-05-30"
capture()	Yes	Multiple meaningful capture calls across product, cart, and checkout routes
identify()	No	No posthog.identify() call anywhere, despite the app having a checkout with user info
Error tracking	Yes	PostHogErrorBoundary wraps the app in entry.client.tsx
Reverse proxy	No	No proxy rewrites configured; no vite.config.ts rewrites or middleware proxy set up

Issues

• No user identification: The shopper app has a checkout form collecting name, email, and address, but posthog.identify() is never called. All events remain anonymous, preventing user-level analytics. Add posthog.identify(userId, { email, name }) during checkout or on an auth event, and posthog.reset() on logout. [MEDIUM]
• No reverse proxy: Client-side PostHog requests go directly to us.i.posthog.com and are susceptible to ad blockers. Configure Vite/React Router rewrites or use PostHog's managed reverse proxy. [MEDIUM]

Other completed criteria

• API key loaded from VITE_PUBLIC_POSTHOG_PROJECT_TOKEN environment variable
• API host loaded from VITE_PUBLIC_POSTHOG_HOST environment variable
• PostHogProvider wraps the app correctly
• PostHogErrorBoundary provides error tracking
• defaults: "2026-05-30" config option correctly set
• Dev-mode validation throws if env vars are missing

---

PostHog insights and events ✅

Filename	PostHog events	Description
entry.client.tsx	captureException (via ErrorBoundary)	PostHogErrorBoundary captures unhandled React errors
products.tsx	product_added, product_category_selected	Tracks add-to-cart from product list and category filter selection
products..tsx	product_added	Tracks add-to-cart from product detail page with quantity
cart.tsx	cart_item_removed, cart_quantity_updated, checkout_started	Tracks cart modifications and checkout initiation
checkout.tsx	order_completed	Tracks order completion with item count and total

Issues

• No issues with event quality — events represent real e-commerce actions with enriched properties, enabling funnel analysis from product browsing through checkout completion. [N/A]

Other completed criteria

• Events represent real user actions (add to cart, checkout, purchase)
• Events enable product insights (product → cart → checkout funnel)
• Events include relevant properties (product_id, category, price, quantity, source)
• No PII in event properties
• Event names are descriptive and use consistent snake_case convention

---

Reviewed by wizard workbench PR evaluator