Skip to content

fix(core): bundle the Faust packages so pages rendered on demand work with Turbopack - #2696

Merged
josephfusco merged 3 commits into
canaryfrom
fix/turbopack-router-context
Oct 23, 2026
Merged

josephfusco merged 3 commits into
canaryfrom
fix/turbopack-router-context

Conversation

@josephfusco

Copy link
Copy Markdown
Member

With Next.js 16's default Turbopack build, next start returned 500 ("NextRouter was not mounted") for every page rendered on demand through [...wordpressNode], on every core release back to 3.4.1, while webpack builds and dev worked; I confirmed this fixes the unmodified getting-started example on Next 16.4.3 in a browser, and CI misses it because the e2e job only runs next build and never serves the app.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Assisting with tracing the production-only router error to Turbopack and verifying the fix in a real app.

@josephfusco josephfusco added [Type] Bug An existing feature is broken [Area] Compatibility WordPress, Next.js, Node.js, and third-party compatibility [Area] Core Issues for the @faustwp/core package labels Oct 23, 2026
@josephfusco
josephfusco marked this pull request as ready for review October 23, 2026 15:17
@josephfusco
josephfusco requested review from a team and colinmurphy as code owners October 23, 2026 15:17
@josephfusco
josephfusco merged commit 3f5ff44 into canary Oct 23, 2026
18 checks passed
@josephfusco
josephfusco deleted the fix/turbopack-router-context branch October 23, 2026 16:29
@github-actions github-actions Bot mentioned this pull request Oct 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Area] Compatibility WordPress, Next.js, Node.js, and third-party compatibility [Area] Core Issues for the @faustwp/core package [Type] Bug An existing feature is broken

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant