Skip to content

fix(error-tracking): init the Next.js browser SDK at the top level of instrumentation-client.ts #443

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ablaszkiewicz merged 1 commit into from
Oct 28, 2026
+1 −0
Merged

fix(error-tracking): init the Next.js browser SDK at the top level of instrumentation-client.ts #443

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions context/commandments.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ commandments:
nextjs:
# Initialization
- For Next.js 15.3+, initialize PostHog in instrumentation-client.ts for the simplest setup
- Call posthog.init at the top level of instrumentation-client.ts. Next.js runs that file once for its side effects and reads only its onRouterTransitionStart export, so an init inside an exported register() or any other function never runs. Write the missing-configuration guard as a top-level if/else around the init

nextjs-feature-flags:
# Client-side feature flags
Expand Down
Loading