[CI] (362fa9c) react-router/saas-template

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: 362fa9c
App: react-router/saas-template
App directory: apps/react-router/saas-template
Workbench branch: wizard-ci-362fa9c-react-router-saas-template
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-02-11T17:51:58.333Z
Duration: 743.5s

[wizard-ci-bot]

Now I have read all the key files. Let me compile the PR evaluation report.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router 7 SaaS template (pastebin app). The integration includes client-side SDK initialization with PostHogProvider, server-side middleware for capturing events with session context, error tracking via captureException in the error boundary, and comprehensive event tracking across authentication, billing, and organization flows.

Files changed	Lines added	Lines removed
26	+939	-147

Confidence score: 4/5 👍

• No reverse proxy configured: Events are sent directly to PostHog's API host, making them susceptible to ad blockers. This is a significant gap for production use. [MEDIUM]
• Missing posthog.identify() call: Users are not explicitly identified with PostHog after login/signup. The middleware uses headers for distinctId but the client-side SDK doesn't have identify() called to link user sessions. [MEDIUM]
• No automatic pageview tracking: The capture_pageview option is not explicitly configured. While PostHog defaults may handle this, explicit configuration would be clearer. [LOW]

---

File changes

Filename	Score	Description
app/entry.client.tsx	4/5	PostHog initialized with PostHogProvider wrapper. Uses env vars correctly with defaults: "2025-05-24" for modern features. Good implementation.
app/root.tsx	4/5	Added PostHog middleware and error boundary capture with captureException. Clean integration with existing code.
app/lib/posthog-middleware.server.ts	4/5	New server middleware creates PostHog client per request with withContext for session linking. Properly shuts down client.
vite.config.ts	5/5	Added SSR noExternal config for posthog-js and @posthog/react - necessary for React Router SSR.
package.json	5/5	Added posthog-js, posthog-node, @posthog/react dependencies. Alphabetically reordered (cosmetic).
.gitignore	5/5	Added .env to gitignore - prevents accidental key exposure.
app/features/billing/billing-action.server.ts	4/5	Tracks checkout_started with relevant properties.
app/features/billing/stripe-event-handlers.server.ts	4/5	Tracks Stripe webhook events with dedicated helper function. Creates new PostHog instance per webhook (acceptable for webhooks).
app/features/billing/contact-sales/contact-sales-action.server.ts	4/5	Tracks contact_sales_submitted event.
app/routes/_user-authentication+/_anonymous-routes+/auth.callback.ts	4/5	Tracks user_signed_up and user_logged_in events with auth method and invite context.
app/routes/_user-authentication+/logout.ts	4/5	Tracks user_logged_out event.
app/features/onboarding/organization/onboarding-organization-action.server.ts	4/5	Tracks onboarding_organization_completed event.
app/features/organizations/create-organization/create-organization-action.server.ts	4/5	Tracks organization_created event.
app/features/organizations/accept-email-invite/accept-email-invite-action.server.ts	4/5	Tracks email_invite_accepted event with role.
app/features/organizations/accept-invite-link/accept-invite-link-action.server.ts	4/5	Tracks invite_link_accepted event.
app/features/user-accounts/settings/account/account-settings-action.server.ts	4/5	Tracks account_settings_updated with updated fields.
app/features/pastebin/paste-helpers.server.ts	5/5	Cosmetic changes only - replaced Infinity with Number.POSITIVE_INFINITY, reformatted code. No functional changes.
app/features/organizations/layout/app-sidebar.tsx	5/5	Cosmetic import reordering only.
app/routes/_authenticated-routes+/organizations_+/+/_sidebar-layout.tsx	5/5	Cosmetic formatting only.
app/routes/_authenticated-routes+/organizations_+/+/dashboard.tsx	5/5	Cosmetic changes - formatting, replaced Infinity with Number.POSITIVE_INFINITY.
app/routes/_authenticated-routes+/organizations_+/+/pastes.tsx	5/5	Cosmetic changes - formatting, import reordering, Number.POSITIVE_INFINITY.
app/routes/_authenticated-routes+/organizations_+/+/pastes..tsx	5/5	Cosmetic formatting only.
app/routes/p..tsx	5/5	Cosmetic formatting only.
app/routes/paste..tsx	5/5	Cosmetic formatting only.
posthog-setup-report.md	5/5	Comprehensive documentation of the integration.
package-lock.json	5/5	Standard lockfile updates for new dependencies.

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	Dependencies properly added, SSR config correct, no build-breaking changes
Preserves existing env vars & configs	Yes	Only adds new PostHog env vars, existing configs preserved
No syntax or type errors	Yes	TypeScript types properly handled with PostHogContext interface
Correct imports/exports	Yes	All imports are valid, middleware properly exported
Minimal, focused changes	Partial	Many files have cosmetic reformatting (import order, Infinity → Number.POSITIVE_INFINITY) that could have been separate PR

Issues

• Cosmetic code changes mixed with feature: The Infinity to Number.POSITIVE_INFINITY changes and import reordering are unrelated to PostHog integration and add noise to the PR. [LOW]

Other completed criteria

• Environment variables documented in setup report
• Build configuration valid with SSR noExternal for PostHog packages
• No hardcoded API keys
• Appropriate error handling with optional chaining (posthog?.capture)
• Clean TypeScript integration with PostHogContext type

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js, posthog-node, @posthog/react in package.json
PostHog client initialized	Yes	Client initialized in entry.client.tsx with PostHogProvider, server middleware creates per-request client
capture()	Yes	Multiple capture calls across auth, billing, organizations, and settings
identify()	No	Missing posthog.identify() call after authentication - users are tracked anonymously
Error tracking	Yes	captureException(error) in root error boundary
Reverse proxy	No	No reverse proxy configured - events go directly to api_host

Issues

• Missing user identification: The integration tracks events but never calls posthog.identify() to associate events with user IDs. This means user sessions won't be properly linked to user profiles in PostHog, limiting cohort analysis and user journey tracking. Should add posthog.identify(userId) after successful login in auth.callback.ts. [CRITICAL]
• No reverse proxy: Events are sent directly to PostHog's API host, making them susceptible to ad blockers. For production use, a reverse proxy (e.g., /ingest route proxying to PostHog) should be configured. [MEDIUM]
• __add_tracing_headers configuration: Uses [window.location.host, "localhost"] which is a newer API for distributed tracing - generally correct but could be documented. [LOW]

Other completed criteria

• API key loaded from environment variable (not hardcoded)
• PostHog host configurable via environment variable
• Server-side middleware properly shuts down PostHog client after request
• Session context passed via withContext() for server-side events
• Client properly wrapped with PostHogProvider
• SSR compatibility handled with Vite config

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
auth.callback.ts	user_signed_up, user_logged_in	Tracks new signups and returning user logins with auth method (email/OAuth) and invite context
logout.ts	user_logged_out	Tracks user logout actions
onboarding-organization-action.server.ts	onboarding_organization_completed	Tracks onboarding funnel completion with org details
create-organization-action.server.ts	organization_created	Tracks new organization creation
accept-email-invite-action.server.ts	email_invite_accepted	Tracks team growth via email invites with role
accept-invite-link-action.server.ts	invite_link_accepted	Tracks team growth via invite links
billing-action.server.ts	checkout_started	Tracks checkout initiation with product/pricing details
stripe-event-handlers.server.ts	checkout_completed, subscription_created, subscription_cancelled	Tracks billing lifecycle events from Stripe webhooks
contact-sales-action.server.ts	contact_sales_submitted	Tracks enterprise lead generation
account-settings-action.server.ts	account_settings_updated	Tracks profile changes with updated fields
root.tsx	capturedException	Error boundary captures unhandled errors

Issues

• Missing paste-related events: No tracking for paste creation, deletion, or viewing - core product actions that would be valuable for product analytics. [MEDIUM]
• No feature flag integration: The integration doesn't leverage PostHog feature flags, which could be valuable for this SaaS template. [LOW]

Other completed criteria

• Events cover full user lifecycle (signup → onboarding → active use → churn)
• Billing funnel fully instrumented (checkout started → completed → subscription lifecycle)
• Team growth metrics captured (invite acceptance)
• Events include relevant properties for segmentation
• No PII in event properties (uses IDs, not emails/names where possible)
• Setup report includes suggested insights and funnel ideas

---

Reviewed by wizard workbench PR evaluator