A build that fails under Turbopack but passes with `next build --webpack` almost always points at webpack-specific configuration, not broken application code.
Five causes explain most reports: ignored `webpack()` config, CommonJS-only dependencies, dynamic imports with cache components, Windows path resolution, and the Babel React Compiler.
The `--webpack` fallback now costs the persistent build cache, memory eviction and `import.meta.glob` support.