• Turbopack automatically finds an optimal chunk configuration by considering download size, the number of HTTP requests, cache reuse, page navigation patterns, and other factors together.
  • Ultimately, depending on chunk size, there is a tradeoff among the number of requests, cache reuse, and file size, and it uses probabilities to find the optimal combination.
  • You can optimize the first page (firstPageLoadPriority) or specific routes (priorityRoutes), and clusters can be used to assign a higher likelihood to navigation between particular routes.
  • generateComponentChunks can be used to make fetching decisions at runtime.