Vite 8 beta reports bigger bundle size than latest non beta #579
Description
Describe the bug
Hello,
I been testing out vite beta in a nuxt application and when I run analyze I been noticing that the report bundle size it's bigger than in the latest version of a non beta.
In one of the applications I work on the brotli bundled change from 800kb to 1.20MB from just changing from vite 7.3.1 to vite 8.0.0 beta 10
I created a two reproduction also using a nuxt app in stackblitz and the same output is noticible:
https://stackblitz.com/edit/github-nwxwdggl?file=package.json
Example from the reproduction in vite 7.3.1 we got a report of around 79kb brotli
https://stackblitz.com/edit/github-nwxwdggl-tevaohly?file=package.json
Example from the reproduction in vite 8.0.0 beta 10 we got a report of 109kb
Reproduction
https://stackblitz.com/edit/github-nwxwdggl
Steps to reproduce
Run pnpm i then run pnpm analyze this will display client build ( the server also shows a difference in bundle size but as the client is more important as more data will go to user browser was focusing on that specific part )
System Info
System:
OS: macOS 26.2
CPU: (11) arm64 Apple M3 Pro
Memory: 7.86 GB / 36.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.21.1 - /Users/user-name/.local/state/fnm_multishells/37733_1769252864148/bin/node
Yarn: 4.12.0 - /Users/user-name/.local/state/fnm_multishells/37733_1769252864148/bin/yarn
npm: 10.9.4 - /Users/user-name/.local/state/fnm_multishells/37733_1769252864148/bin/npm
bun: 1.1.38 - /opt/homebrew/bin/bun
Browsers:
Brave Browser: 144.1.86.139
Chrome: 144.0.7559.97
Firefox Developer Edition: 147.0
Safari: 26.2
npmPackages:
vite: 8.0.0-beta.10 => 8.0.0-beta.10Used Package Manager
pnpm
Logs
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.