Repository navigation
fix(core): bundle the Faust packages so pages rendered on demand work with Turbopack - #2696
Merged
Merged
Conversation
josephfusco
marked this pull request as ready for review
October 23, 2026 15:17
Merged
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.
With Next.js 16's default Turbopack build,
next startreturned 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 runsnext buildand 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.