Turbopack: fix split_module correctness for app-router (#95522)
Turbopack: fix split_module correctness for app-router - Don't split the generated __nextjs-internal-proxy. client-reference proxy module. Its exports are all used, so splitting yields no benefit and duplicates its <exports> part in the module graph, tripping the duplicate-ident check in ModuleGraph::from_graphs. - Pass the original comments to each fragment so magic-comment annotations (turbopackChunkingType, turbopackExports) are still parsed. Fragment ASTs keep their original spans, so comments resolve at the same byte positions. Without this, references fall back to defaults (ChunkingType::Shared -> Parallel), breaking app-router layout-segment chunk groups.
Showing
Please
register
or
sign in
to comment