fix: stop claiming error tracking is configured in JS web outro#720
Draft
posthog[bot] wants to merge 1 commit into
Draft
fix: stop claiming error tracking is configured in JS web outro#720posthog[bot] wants to merge 1 commit into
posthog[bot] wants to merge 1 commit into
Conversation
The default `posthog-integration` flow only installs an `integration`-category skill (error-tracking skills are explicitly excluded), so client-side exception capture is never wired up for plain JavaScript (Web) projects. The outro still told users it "Configured autocapture, error tracking, and event capture", over-promising a product the default flow doesn't set up. Correct the copy to reflect what posthog-js actually does by default (autocapture + event capture). Generated-By: PostHog Code Task-Id: 266ea7fd-4170-47f1-991e-479e7c587e55
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
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.
Problem
Developers who run
npx @posthog/wizardon a plain JavaScript (Web) project getproduct analytics, but the javascript-web outro tells them it "Configured
autocapture, error tracking, and event capture". The default
posthog-integrationflow only installs anintegration-category skill andexplicitly excludes error-tracking skills, so client-side exception capture is
never wired up. The result is an over-promise: users expect errors to show up in
PostHog, see nothing, and churn toward Sentry — a public churn signal where a
developer twice questioned what PostHog is even for. The default flow is
high-volume (25,547
setup wizard finishedevents in 30 days), so this is abroad onboarding-trust issue, not a one-off.
Why: the wizard should not claim it set up a product it didn't. This removes
the false promise that drives the churn-to-Sentry confusion.
Changes
Correct the javascript-web outro copy to reflect what
posthog-jsactually doesby default:
Configured autocapture and event capture(dropping the"error tracking" claim).
Scope note: this PR only fixes the inaccurate copy — the one piece fully ownable
and verifiable in this repo. Actually enabling client-side error tracking /
session replay in the default flow is a larger, deliberately out-of-scope change:
the SDK init code is generated by context-mill
integration skills,
session_recording_opt_in/autocapture_exceptions_opt_indefault off server-side on new projects, and offering these as first-class
post-setup add-ons would mean extending the
AdditionalFeaturequeue (today onlyllm) with new TUI opt-in screens. That gap is real but spans repos and is aproduct decision; this change just stops the wizard from over-promising in the
meantime.
Test plan
pnpm build && pnpm test— 1054 tests pass, snapshots unchanged.pnpm fix— clean.javascript-webmade the client-side "error tracking" claim; Python/Railsserver-SDK outros legitimately auto-capture exceptions and were left untouched.
Created with PostHog Code from an inbox report.