Repository navigation
[CI] (3f39e0e) next-js/15-app-router-todo - #4163
Closed
wizard-ci-bot[bot] wants to merge 1 commit into
Closed
wizard-ci-bot[bot] wants to merge 1 commit into
wizard-ci-bot[bot] wants to merge 1 commit into
Conversation
Author
PR Evaluation ReportSummaryThis PR integrates PostHog into a Next.js 15 App Router todo application. Client-side initialization is done via
Confidence score: 4/5 👍
File changes
App sanity check
|
| Criteria | Result | Description |
|---|---|---|
| App builds and runs | No | OpenTelemetry package versions (^0.222.0, ^2.11.0) are almost certainly non-existent, causing npm install to fail |
| Preserves existing env vars & configs | Yes | Existing code and configs are untouched; only additions made |
| No syntax or type errors | Yes | All TypeScript syntax is valid |
| Correct imports/exports | Yes | All imports resolve correctly (posthog-js, next/server, instrumentation exports) |
| Minimal, focused changes | Yes | All changes relate directly to PostHog integration |
| Pre-existing issues | None | Base app appears well-structured |
Issues
- Hallucinated OpenTelemetry versions:
@opentelemetry/sdk-logs@^0.222.0,@opentelemetry/api-logs@^0.222.0,@opentelemetry/exporter-logs-otlp-http@^0.222.0, and@opentelemetry/resources@^2.11.0are almost certainly non-existent versions. These packages were in the 0.5x.x and 1.2x.x ranges respectively. Fix: use the actual latest versions from npm. [CRITICAL] - Outdated defaults date:
defaults: '2026-01-30'ininstrumentation-client.tsshould be'2026-05-30'to use the latest recommended configuration defaults. [LOW]
Other completed criteria
- Environment variables documented in
.env.example - Build configuration structure (package.json scripts) is valid apart from version issue
- Existing app functionality preserved — API routes still work, only PostHog logging added after response
PostHog implementation ⚠️
| Criteria | Result | Description |
|---|---|---|
| PostHog SDKs installed | Yes | posthog-js@^1.434.12 added to dependencies |
| PostHog client initialized | Yes | posthog.init() in instrumentation-client.ts with env-based token and host, following Next.js docs pattern |
| capture() | Yes | Three meaningful client-side captures: todo_created, todo_completion_changed, todo_deleted |
| identify() | No | No identify() call anywhere in the app. No reset() on logout either. |
| Error tracking | Yes | global-error.tsx with posthog.captureException(error) and capture_exceptions: true in init config |
| Reverse proxy | No | No rewrites in next.config.ts to proxy PostHog requests |
Issues
- No reverse proxy: Next.js rewrites should be configured in
next.config.tsto proxy/ingest/*requests to PostHog, preventing ad blockers from intercepting events. See the Next.js proxy docs. [MEDIUM] - No user identification: No
posthog.identify()orposthog.reset()calls. Even without a current auth system, the todo app should prepare for future user identification or at minimum document the gap. [MEDIUM]
Other completed criteria
- API key loaded from
NEXT_PUBLIC_POSTHOG_PROJECT_TOKENenvironment variable (not hardcoded) - API host loaded from
NEXT_PUBLIC_POSTHOG_HOSTenvironment variable - Initialization follows the recommended
instrumentation-client.tspattern from PostHog's Next.js docs - Server-side OTLP logging approach is functional (if dependencies install correctly)
PostHog insights and events ✅
| Filename | PostHog events | Description |
|---|---|---|
components/todos/todo-list.tsx |
todo_created, todo_completion_changed, todo_deleted |
Client-side captures for all todo CRUD operations with enriched properties |
app/global-error.tsx |
captureException |
Client-side error boundary capturing unhandled exceptions |
instrumentation-client.ts |
capture_exceptions: true |
Automatic exception autocapture enabled |
instrumentation.ts |
OTLP log: Todo API mutation completed |
Server-side structured logs for todo mutations (created/updated/deleted) |
Issues
- No issues with event quality.
Other completed criteria
- Events represent real user actions (creating, completing, deleting todos)
- Events enable product insights — can build todo creation funnel, completion rates, deletion patterns
- Events include relevant properties (
has_description,initial_completed,completedstatus) - No PII in event properties
- Event names follow consistent snake_case convention and are descriptive
Reviewed by wizard workbench PR evaluator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated wizard CI run
Source: wizard-pr
Trigger ID:
3f39e0eApp:
next-js/15-app-router-todoApp directory:
apps/next-js/15-app-router-todoWorkbench branch:
wizard-ci-3f39e0e-next-js-15-app-router-todoWizard branch:
release-please--branches--main--components--wizardContext Mill branch:
mainPostHog (MCP) branch:
masterTimestamp: 2026-09-23T22:07:25.957Z
Duration: 449.9s
YARA Scanner