[CI] (362fa9c) nuxt/movies-nuxt-3-6

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: 362fa9c
App: nuxt/movies-nuxt-3-6
App directory: apps/nuxt/movies-nuxt-3-6
Workbench branch: wizard-ci-362fa9c-nuxt-movies-nuxt-3-6
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-02-11T17:38:45.972Z
Duration: 578.9s

[wizard-ci-bot]

---

PR Evaluation Report

Summary

This PR adds a comprehensive PostHog integration to a Nuxt 3.6 Movies application. It includes client-side SDK initialization via a plugin, server-side tracking with posthog-node in API routes, user identification on login/logout, error tracking via Vue error hooks, and event tracking across multiple user interactions (media views, search, video plays, external link clicks).

Files changed	Lines added	Lines removed
18	+488	-86

Confidence score: 3/5 🤔

• Missing page view tracking: No automatic pageview capture configured in PostHog initialization - relies only on manual event captures [MEDIUM]
• Inefficient PostHog client instantiation in API routes: Creates and shuts down PostHog client on every request, causing performance overhead [MEDIUM]
• No reverse proxy configuration: Missing reverse proxy setup to circumvent ad-blockers when sending events to PostHog [MEDIUM]
• Server-side tracking headers dependency undocumented: Server routes rely on x-posthog-session-id and x-posthog-distinct-id headers but client isn't configured with __add_tracing_headers [MEDIUM]

---

File changes

Filename	Score	Description
plugins/posthog.client.ts	4/5	New file - PostHog client plugin with proper initialization, debug mode in dev, and Vue error hook for exception capture
nuxt.config.ts	4/5	Added runtime config for PostHog keys and host via environment variables
package.json	5/5	Added posthog-js and posthog-node dependencies
composables/useAuth.ts	4/5	Added identify on login, reset on logout, capture for login/logout/failure events. Minor style changes (arrow to function syntax)
server/api/auth/login.post.ts	3/5	Added server-side PostHog tracking but creates new client instance per request with shutdown - inefficient pattern
server/api/auth/logout.post.ts	3/5	Same inefficient pattern - creates/shuts down PostHog client per request
error.vue	4/5	Added error page tracking and exception capture for non-404 errors
components/ExternalLinks.vue	5/5	Added external link click tracking with platform and URL properties
components/video/Card.vue	5/5	Added video play tracking with name, type, and key properties
components/NavBar.vue	5/5	Minor attribute ordering change only
pages/[type]/[id].vue	5/5	Added media view tracking with relevant properties
pages/person/[id].vue	5/5	Added person view tracking
pages/search.vue	5/5	Added search tracking with query property
pages/login.vue	5/5	Minor formatting changes (self-closing tags, style adjustments)
middleware/auth.global.ts	5/5	Minor formatting changes only
types/posthog.d.ts	5/5	New file - TypeScript declarations for PostHog in Nuxt
posthog-setup-report.md	4/5	Documentation of implementation - references .env file creation but file not in PR
pnpm-lock.yaml	5/5	Lock file updated with new dependencies

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	No syntax errors, proper imports, dependencies installed
Preserves existing env vars & configs	Yes	Only additions to nuxt.config.ts, no removals
No syntax or type errors	Yes	TypeScript declarations added for PostHog, proper typing throughout
Correct imports/exports	Yes	All imports are correct, plugin properly exports PostHog
Minimal, focused changes	Yes	Changes are focused on PostHog integration with minor formatting cleanup

Issues

• Missing .env file: The posthog-setup-report.md claims an .env file was created but it's not in the committed files. Users need to manually create environment variables. [LOW]

Other completed criteria

• Environment variables properly documented via runtime config
• Build configuration is valid
• Consistent with existing Nuxt 3 patterns
• Uses optional chaining (posthog?.capture) for safety
• Proper TypeScript module augmentation for NuxtApp

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.237.1 and posthog-node@^4.17.2 in dependencies
PostHog client initialized	Yes	Client plugin (posthog.client.ts) initializes via posthog.init() with runtime config
capture()	Yes	Multiple capture calls across components and pages
identify()	Yes	posthog.identify(response.user) on login, posthog.reset() on logout
Error tracking	Yes	Vue error hook captures exceptions, error.vue captures page views and exceptions
Reverse proxy	No	No reverse proxy configuration to circumvent ad-blockers

Issues

• No reverse proxy setup: The integration does not include a reverse proxy configuration (via nitro routes or similar) to avoid ad-blocker issues. This could result in significant data loss from users with ad-blockers. [MEDIUM]
• Server-side PostHog inefficiency: The server routes create a new PostHog instance and call shutdown() on every single request. This is inefficient and could cause performance issues under load. Should use a singleton pattern or middleware. [MEDIUM]
• Missing __add_tracing_headers configuration: Server routes comment references "Relies on __add_tracing_headers being set in the client-side SDK" but this option is not configured in the client plugin initialization. The headers won't be sent. [MEDIUM]
• No automatic pageview tracking: The capture_pageview option isn't explicitly set. Manual events track views but standard pageview tracking is missing. [LOW]

Other completed criteria

• API key loaded from environment variable (not hardcoded)
• API host configurable via environment variable
• Debug mode enabled in development
• Proper cleanup with posthog.reset() on logout
• Exception capture via captureException()
• No PII in event properties beyond username

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
composables/useAuth.ts	user_logged_in, user_logged_out, login_failed	Tracks authentication funnel with user identification
pages/search.vue	search_performed	Captures search queries for search analytics
pages/[type]/[id].vue	media_viewed	Tracks movie/TV show views with type, ID, title, and rating
pages/person/[id].vue	person_viewed	Tracks person/actor page views
components/video/Card.vue	video_played	Tracks video trailer plays with metadata
components/ExternalLinks.vue	external_link_clicked	Tracks outbound link clicks by platform
error.vue	error_page_viewed, captureException	Tracks error pages and captures non-404 exceptions
server/api/auth/login.post.ts	server_login_success, server_login_error	Server-side login tracking
server/api/auth/logout.post.ts	server_logout	Server-side logout tracking

Issues

• Duplicate tracking for auth events: Both client-side (useAuth.ts) and server-side (login.post.ts, logout.post.ts) track login/logout events. This will result in duplicate events unless client headers are properly configured. [LOW]

Other completed criteria

• Events capture meaningful user actions (views, searches, plays, clicks)
• Properties are relevant and useful for analysis (media type, search query, platform)
• Events enable building funnels (login success vs failure)
• Error tracking captures both custom events and exceptions
• Events cover key product flows (authentication, content discovery, engagement)

---

Reviewed by wizard workbench PR evaluator