Build times increased ~20% upgrading to Vite 8

[aeharding]

My build times increased from 38s to 45s (~20% slower).

App: https://github.com/aeharding/voyager

Change: https://github.com/aeharding/voyager/pull/2231/changes

vite v7.3.1 building client environment for production...
✓ 3187 modules transformed.
dist/assets/polyfills-legacy-DtUWSK81.js     77.65 kB │ gzip:  28.45 kB
dist/assets/index-legacy-JKZ5oeSt.js      3,706.20 kB │ gzip: 999.84 kB
dist/manifest.json                     1.20 kB │ gzip:     0.48 kB
dist/index.html                       17.80 kB │ gzip:     2.02 kB
dist/assets/index-D0Ra0OPO.css       123.79 kB │ gzip:    23.87 kB
dist/assets/polyfills-Dm9UlOxn.js     14.83 kB │ gzip:     5.99 kB
dist/assets/index-DIEzVgrv.js      3,674.58 kB │ gzip: 1,022.72 kB
✓ built in 38.27s

PWA v1.2.0
mode      generateSW
precache  10 entries (7456.91 KiB)
files generated
  dist/sw.js
  dist/workbox-07003d38.js

vite v8.0.0 building client environment for production...
✓ 3012 modules transformed.
computing gzip size...
dist/manifest.json                            1.19 kB │ gzip:     0.48 kB
dist/index.html                              17.99 kB │ gzip:     2.09 kB
dist/assets/index-Djql1zH7.css              151.61 kB │ gzip:    24.72 kB
dist/assets/rolldown-runtime-COnpUsM8.js      0.81 kB │ gzip:     0.46 kB
dist/assets/polyfills-B5_lQbJF.js            12.92 kB │ gzip:     4.99 kB
dist/assets/index-D87IV7gB.js             3,614.86 kB │ gzip: 1,000.59 kB

[PLUGIN_TIMINGS] Warning: Your build spent significant time in plugins. Here is a breakdown:
  - vite-plugin-svgr (45%)
  - rolldown:vite-resolve (36%)
  - @rolldown/plugin-babel (11%)
  - vite:css (6%)
See https://rolldown.rs/options/checks#plugintimings for more details.

✓ built in 45.11s

PWA v1.2.0
mode      generateSW
precache  12 entries (7526.79 KiB)
files generated
  dist/sw.js
  dist/workbox-07003d38.js

Just thought I'd mention, if anyone has any ideas why my build times would increase?

[aniruddhaadak80]

@aeharding A 20% increase could be due to changes in the default target (esbuild vs terser) or source map generation in v8.
Check if build.minify changed defaults or if new polyfills are being included.
You can run vite build --debug or use rollup-plugin-visualizer to see if a specific chunk grew unexpectedly.

[aeharding]

Just to be clear, I'm talking about the time it takes to build in seconds, not the size of the output chunks.

[WoodyWoodsta]

@aniruddhaadak80 is likely a bot by the way. They've commented on almost every unanswered discussion across a number of repos I've looked at today.

[aniruddhaadak80]

@aniruddhaadak80 is likely a bot by the way. They've commented on almost every unanswered discussion across a number of repos I've looked at today.

I understand how frustrating it's.

I actually gave my GitHub access to openclaw , and I can't able stop this now.

I am trying to resolve this problem. It will resolve soon, (hope so)

And I just stopped this, but for the deletion of my comments I need to do that manually for all ( I just can't trust openclaw now to close all comments)

Do you know any other option so that I just remove the mess ( all unessary comments in various discussions,)

any type of help would be highly appreciated 👍