Skip to content

Limitations

These constraints match the current MVP scope. They are not promises about future versions—see the roadmap.

Imports

  • Imports are not rewritten. React imports (react, useState, etc.) are not automatically turned into Vue imports. You must adjust import lines and library usage after conversion.

One component per file

  • Multiple components per file and complex re-export patterns are not fully modeled. Prefer one primary component per file for best results.

Libraries and design systems

  • Library-specific prop names (e.g. Material UI vs a Vue port) may not map one-to-one. Expect manual cleanup for third-party components.

Effect cleanup

  • useEffect cleanup (return () => …) may require manual translation to Vue watch / onMounted teardown. See React → Vue mapping.

Coverage

  • Real-world codebases use patterns the parser does not handle yet. If something fails, consider reducing the component to a minimal repro and opening an issue or adding a test fixture (see Contributing).

What is not available today

  • Vue, Svelte, Solid, or Qwik as input — not implemented; only React → Vue.
  • Emit targets other than Vue 3 SFC — not implemented in this version.

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