turbopackModuleFragments split_module index mismatch causes panic on empty groups
split_module mixes group indices and compacted module positions; empty groups cause off-by-one leading to out-of-bounds panic in module_fragments/graph.rs:746.

Affected version
Reports that share this version, grouped in one feed.
split_module mixes group indices and compacted module positions; empty groups cause off-by-one leading to out-of-bounds panic in module_fragments/graph.rs:746.
When middleware.ts exists, Next.js normalizes _next/data URLs before config redirects run, causing redirects to match internal data requests and return props from the wrong page. This breaks client-side navigation, while the absence of middleware avoids the issue.
In Next.js Pages Router, during a shallow navigation, Router.getRouteInfo() may return a cached { __appRouter: true } prefetch marker instead of actual route info, leading to undefined Component and pageProps, crashing _app and preventing navigation.
Next.js reports an error that mentions 'searchParams' when the actual inaccessible dynamic data is 'params' inside a 'use cache' context. This misleads developers by pointing to the wrong property, causing confusion and wasted debugging time.