How Turbopack chunks your JavaScript

But then we'd lose caching. If every page uses <Footer />, its code ends up inside every page's chunk. A visitor who opens four pages downloads the same footer code four times. So we need something even more fine-grained. What if every module got its own chunk? Nothing would ever be over-shipped, and a module shared between pages would only download once. One chunk per module: 355 separate chunks,

[efcl]

TurbopackのChunk分割アルゴリズムについて。 Chunkのマージによるリクエスト数と転送量のトレードオフについて解説されている。 Next.js 16.3の`generateComponentChunks`では、ビルド時にはChunk GroupとChunkを生成する。Runtimeでナビゲーシ