Tracking Vue Vapor's path to 10KB
Automated benchmarks comparing Vue Vapor Mode vs Classic Vue bundle sizes. Watch the progress as Vapor evolves toward its promised ~10KB gzipped target.
Current Benchmark
Benchmark History
| Version | Vapor (gzip) | Classic (gzip) | Savings | Date |
|---|---|---|---|---|
| Loading history... | ||||
Understanding the Numbers
Why is the bundle growing? During alpha, the Vue team is porting more functionality into Vapor mode. Each release adds features, which temporarily increases size.
When will it drop? Once Vapor is feature-complete, apps can drop the Virtual DOM runtime entirely (@vue/runtime-core, @vue/runtime-dom). That's when we'll see the jump from ~22 KB down to the ~10 KB target.
What is this?
A tracker for Vue Vapor Mode's evolution toward standalone builds.
-
[*]
Vue Vapor Mode is Vue 3.6's new compilation strategy that eliminates the Virtual DOM
-
[*]
The 10KB promise Vapor-only builds should eventually drop to ~10KB gzipped
-
[*]
Currently bundled Vue 3.6 alpha still includes runtime-core alongside runtime-vapor
-
[*]
This tracker monitors each Vue 3.6.x release to watch the progress
How It Works
Daily Check
GitHub Actions checks for new Vue 3.6.x releases every day
Auto Benchmark
When a new version is found, it builds both Vapor and Classic variants
PR Created
A pull request is opened with the benchmark results for review
History Updated
Once merged, the benchmark history is updated and this page reflects the latest data
Run It Yourself
# Clone the repo
git clone https://github.com/frankdierolf/vuevapor-watch
cd vuevapor-watch
# Install dependencies
npm install
# Run the benchmark
npm run benchmark
# Or inspect the builds (readable output)
npm run benchmark:inspect