Replace the Alpine ownership runtime with Vue - #137
Open
JuroOravec wants to merge 87 commits into
Open
JuroOravec wants to merge 87 commits into
JuroOravec wants to merge 87 commits into
Conversation
This was referenced Sep 22, 2026
This branch has not been deployed
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.
Citry's Alpine renderer rebuilt component ownership in Python and again in the browser, then used range comments and a custom morph planner to preserve scopes across server updates. This change replaces that path with server-compiled Vue component definitions and retained native Vue instances. Interactive templates now use Vue directives and Options, while static output continues to serialize without loading a browser runtime.
The migration removes the ownership crate, client-graph protocol, Alpine/morph assets, and their browser reconstruction code. It adds the native Rust Vue compiler, typed prepared rendering, native component and slot relationships, component/marker Events targeting,
Citry.vue, andonServerRender. The compiler uses the documented, MIT-licensed, Citry-patched Vize 0.420.0 sources merged separately in #140 so request-time compilation remains Node-free. Citry UI, i18n, Events, starters, docs, the linter, LSP, and VS Code extension are migrated to the same model. The Python component API remains the rendering entry point; the public browser migration and breaking changes are listed inCHANGELOG.md. Compiled templates support the qualified Vue syntax documented in the guide; Vue built-ins such asTeleport,Transition,Suspense, andKeepAliveremain outside this release's compiled-template contract.Component wrappers can now forward undeclared Vue attributes and listeners explicitly with
inheritAttrs: falseand<c-Child v-bind="$attrs" />. The exact authoredv-on="listeners"object form is preserved through parser provenance, prepared metadata, cache replay, native compilation, LSP analysis, and the browser protocol. Plain component attributes remain Python kwargs, and Python data cannot manufacture executable Vue directives.Benchmark probes, framework-comparison projects, qualification captures, and generated performance reports are deliberately excluded from this promotion. The retained design documents describe the architecture and decisions without linking to those local artifacts.
Validation:
The refreshed GitHub Actions matrix is running after incorporating #140 and the final focused commits.