feat: add Vue Vapor Mode benchmark - #35
Open
zhsama wants to merge 1 commit into
Open
Conversation
zhsama
marked this pull request as ready for review
August 26, 2026 08:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
<script setup vapor>components andcreateVaporApp.Why
Vue Vapor Mode uses compiler-generated direct DOM updates instead of the traditional virtual DOM path. Adding it as a separate implementation makes that mode measurable without changing the existing Vue benchmark.
Impact
The existing framework implementations remain unchanged. Contributors can run the new app through the generated
vue-vaporroot commands.Validation
npm run build:vue-vapornpm run lint:vue-vapornpx playwright test --config=tests/config/playwright-vue-vapor.config.js --reporter=dot— 22 passedpython scripts/verify/validate_schemas.py