Rollup manualChunks: Splitting Vendor Code for Real Caching Wins
Learn how Rollup's manualChunks option separates vendor libraries from application code, improving browser cache reuse and reducing re-downloads on every deploy.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Rollup's manualChunks option separates vendor libraries from application code, improving browser cache reuse and reducing re-downloads on every deploy.
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
Goal Reduce build‑time noise from oversized‑chunk warnings without hiding genuine bundle regressions. Current Behavior Vite emits a warning when a Rollup chunk exceeds build.chunkSizeWarningLimit (default 500 kB). The threshold is evaluated against the uncompressed, minified size, while the CLI reports both raw and gzip sizes. Unresolved Decision Teams can e