fix(nextjs): build client analytics example with React 19.3 - #46
Merged
Merged
Conversation
This was referenced Sep 26, 2026
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.
Root cause
Dependabot opened separate React and React DOM updates (#41, #42). Updating one alone can select incompatible peers, and the Next.js example is excluded from the pnpm workspace/CI. On the unchanged
mainSHAad84d64fa949bc4fb28115688c5f440aa737d798, its production build fails while collecting page data:createContext is not a function. The server layout imports a client-only analytics provider.Repair
>=19.3.0.Files:
.github/workflows/ci.yml,examples/nextjs/app/{layout,providers}.tsx,examples/nextjs/{package.json,package-lock.json,tsconfig.json,next-env.d.ts}.Local verification
All commands ran in an isolated external-drive worktree.
hk check --all --slow,pnpm install --frozen-lockfile,pnpm build,pnpm pack --recursive --dry-run,pnpm typecheck,pnpm test,pnpm audit,actionlint,git diff --check,npm ci --ignore-scriptsinexamples/nextjs,npm run buildthere, andnpm audit --audit-level highthere each exited 0. Root command logs and exit codes:/Volumes/Code/Sources/.dev-storage/mathematic-inc-monitor/2026-09-25T1501Z-full.IgHeRG/logs/repairs/alyt-react/final/results.tsv; example logs: adjacentexample-ci-{install,build,audit}.log. The unchanged-main example failure is captured inlogs/native/alyt/example-baseline-build.log.Merge gate
Do not merge until all exact PR-head strict checks, reviews, and ruleset conditions are green. The current default-branch SHA has successful Actions CI/hk/Analyze/gate contexts but is missing its strict GitHub Advanced Security
CodeQLprovider-57789 context; post-merge verification of that context remains an unresolved gate.