cross-framework

Appearance

cross-frameworkReact → Vue 3, today

Babel parses your TSX; the compiler builds an IR, then prints Vue 3 SFCs—hooks, JSX (lists, conditionals, spreads), and props flow through structured transforms—not regex patches.

Getting started
Compiler features
Live playground

Parser (react.ts)

Resolves default/named exports through memo, forwardRef, and Object.assign; walks setup for useState, useRef, useMemo, useEffect, subcomponents, and verbatim blocks.

Vue codegen (vue.ts)

Emits script setup with ref, computed, watch, watchEffect, onMounted, defineProps, toRefs, and templates with v-bind, v-if, v-for, and className→class.

Hooks → composition API

State and refs become ref(); memos become computed(); effects map to watch, watchEffect, or onMounted with dependency rewriting for Vue.

JSX & template IR

Spreads, event props, ternaries, &&, .map lists with keys, fragments, and component vs DOM tags—lowered to TemplateNode then printed as Vue markup.

Playground + CLI

Same convertCode in the browser API, the Nuxt demo, and cross-framework convert on disk.

Documented surface

Full parser/codegen inventory on the Compiler features page; limitations and roadmap call out what is not implemented yet.

What works right now ​

Only React (JSX / TSX) → Vue 3 SFC is implemented. Other framework pairs appear on the roadmap only.

Deep dive: Compiler features lists everything the parser and codegen handle today (including className / :class, boolean attrs, effect deps, handler stubs, and subcomponents via h()).

Try it ​

Contact: parsajiravand@gmail.com — questions, feedback, or interest in joining the team. See Contact.

Repository layout ​

PathRole
src/Parser, IR, Vue codegen, CLI entry
website/Nuxt playground (not bundled with the npm package)
docs/This VitePress site

Questions? parsajiravand@gmail.com · MIT License · BRANDING.md for name / fork policy · https://cross-framework.netlify.app/ · https://cross-framework-doc.netlify.app/

Copyright © present cross-framework contributors