Vite build.chunkSizeWarningLimit: deciding between raising the limit or manual chunking

Goal

When a CI pipeline reports a failed deployment, the first step is to determine whether a Vite build warning about oversized chunks is the root cause or merely a side effect. The warning appears after a production build if any emitted chunk exceeds the build.chunkSizeWarningLimit (default 500 kB of minified, uncompressed output). Because the build still succeeds, the warning can mask unrelated failures.

Constraints and Uncertainty

The warning threshold is per‑chunk, so a shared dependency imported by several routes may trigger a single large chunk. Adjusting chunkSizeWarningLimit hides the signal but does not address the underlying bundle size, while using build.rollupOptions.output.manualChunks can split the dependency but introduces potential circular import or load‑order issues if misconfigured. Teams must decide how to balance diagnostic noise against actual bundle optimization.

Specific Questions

• Should we raise build.chunkSizeWarningLimit to suppress the warning, or should we invest time in configuring manualChunks to split large dependencies?
• What impact does a higher limit have on the perceived bundle size versus actual network transfer size for end users?
• How can we reliably determine whether the warning is a symptom of a genuine deployment failure or a benign advisory?