Turbopack: shorter error message for ModuleBatchesGraph::get_entry_index#92828
Merged
Conversation
nextjs-bot
added
created-by: Turbopack team
mischnic
approved these changes
Apr 15, 2026
Contributor
Failing test suitesCommit: 2009f96 | About building and testing Next.js
Expand output● missing-suspense-with-csr-bailout › useSearchParams › should pass build if useSearchParams is wrapped in a suspense boundary
Expand output● app dir - metadata dynamic routes suspense › should render metadata in head when root layout is wrapped with Suspense for bot requests |
Merging this PR will not alter performance
Comparing 
Footnotes
|
Contributor
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URL |
Contributor
Failing test suitesCommit: 2009f96 | About building and testing Next.js
Expand output● missing-suspense-with-csr-bailout › useSearchParams › should pass build if useSearchParams is wrapped in a suspense boundary
Expand output● app dir - metadata dynamic routes suspense › should render metadata in head when root layout is wrapped with Suspense for bot requests |
sokra
added a commit
that referenced
this pull request
Apr 15, 2026
…dex (#92828) ### What? In `ModuleBatchesGraph::get_entry_index`, when an entry module is not found in the graph, the error message included the full list of all possible entries (with their resolved string identifiers). This is an expensive operation that requires async resolution of every entry's `ident().to_string()`. ### Why? In production builds, this verbose error output is unnecessary overhead and produces very long error messages that are hard to read. The list of possible entries is only useful during development/debugging. ### How? Gate the expensive "possible entries" diagnostic behind `cfg!(debug_assertions)`. In release builds, a short `bail!("Entry is not in graph")` is used instead. In debug builds, the full diagnostic with all possible entry identifiers is still shown to aid debugging. This mirrors the same approach already applied to `ChunkGroupInfo::get_index_of`. <!-- NEXT_JS_LLM_PR -->
This was referenced Apr 23, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
What?
In
ModuleBatchesGraph::get_entry_index, when an entry module is not found in the graph, the error message included the full list of all possible entries (with their resolved string identifiers). This is an expensive operation that requires async resolution of every entry'sident().to_string().Why?
In production builds, this verbose error output is unnecessary overhead and produces very long error messages that are hard to read. The list of possible entries is only useful during development/debugging.
How?
Gate the expensive "possible entries" diagnostic behind
cfg!(debug_assertions). In release builds, a shortbail!("Entry is not in graph")is used instead. In debug builds, the full diagnostic with all possible entry identifiers is still shown to aid debugging.This mirrors the same approach already applied to
ChunkGroupInfo::get_index_of.