Repository navigation
feat: add initial Vue Vapor support - #1174
Merged
Merged
Conversation
✅ Deploy Preview for vue-devtools-docs canceled.
|
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
commit: |
webfansplz
changed the title
webfansplz
force-pushed
the
feat/vapor-support
branch
from
October 20, 2026 07:31
4c914c6 to
c7cc486
Compare
Add the Vapor support plan, a Vapor playground, duck-typed Vapor guards in the kit, a `record.vapor` flag for Vapor apps, and a vue@3.6.0-rc.5 test-only alias. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
webfansplz
force-pushed
the
feat/vapor-support
branch
from
October 21, 2026 02:10
c7cc486 to
e62bccd
Compare
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.
First step of Vue Vapor (3.6) support. The full plan is in
plans/vapor-support.md; later phases land as separate PRs.Changes
plans/vapor-support.md: Vapor support plan (breakage inventory, phases, testing, open questions).playground/vapor(pnpm play:vapor): a purecreateVaporApptree and acreateApp+vaporInteropPluginmixed tree.packages/kit/src/runtime/vapor.ts: duck-typed guards (isVaporInstance,isVaporApp,isVaporFragment,isInteropFragment,isTeleportFragment,isForFragment) andVFfragment bits. No@vue/runtime-vaporimport, so the kit still works with Vue 3.5.AppRecord.vaporis set whenapp.vapor === true.vue-3.6(npm:vue@3.6.0-rc.5) catalog alias as a root devDependency, for tests only. The package root resolves to a Node build without Vapor, so tests import thevue.runtime-with-vapor.esm-browser.jsbundle (typed bytests/vue-3.6.d.ts).Tests
tests/unit/runtime/vapor.test.ts: guards, a realcreateVaporAppmount, and therecord.vaporflag.pnpm test: 68 files / 405 tests pass.🤖 Generated with Claude Code