[!WARNING] Vize is experimental and in its Real World Testing phase — not a completely production-ready toolchain yet. Breaking changes and behavior that diverges from Vue are expected. Review the stability guide, production-readiness checklist, and support policy before adopting it.
What Is Vize?
Vize is a Rust-native toolchain for Vue. One shared parser powers compilation, linting, type-checking, formatting, and editor tooling, so the Vue workflow runs on the same core instead of a patchwork of disconnected tools.
It plugs into the tools you already use: @vizejs/vite-plugin for Vite, @vizejs/nuxt for Nuxt,
the vize package for project scripts, oxlint-plugin-vize for Oxlint, and
@vizejs/vite-plugin-musea for the component gallery.
Usage
Vize is a toolchain you add to a Vue app. It does not scaffold the app itself. Pick the shortest path that matches your project; the docs have the rest.
Drop-in
On a Vue 3 + Vite app, replace @vitejs/plugin-vue with @vizejs/vite-plugin. Your SFCs stay as
they are.
npm i -D @vizejs/vite-plugin
// vite.config.ts
import { defineConfig } from "vite";
import vize from "@vizejs/vite-plugin";
export default defineConfig({
plugins: [vize()],
});
Then use the same dev / build scripts as before. This swaps SFC compilation only. Lint, format,
and type-check stay on your current tools until you add them. The claim is Vue 3 SFCs in Vite — see
Drop-in Scope.
Nuxt apps should use @vizejs/nuxt instead of wiring the Vite plugin by hand.
Type checking
Type-check .vue files with TypeScript 7.1 or newer and Vize's content mapper.
tsrs can run the same tsconfig.
npm i -D vize typescript@beta
{
"contentMappers": [{ "package": "vize", "extensions": [".vue"] }]
}
npx tsc --runExternalCode --noEmit -p tsconfig.json
npx tsrs --runExternalCode --noEmit -p tsconfig.json
typescript@beta is the 7.1 beta, the first release that includes content mappers.
After 7.1 is stable, install typescript at 7.1 or newer and keep the same command.
Details are in the type checking guide.
New setup
Create a Vue + Vite or Nuxt app first, then let vize init wire the toolchain.
Vue + Vite:
npm create vue@latest my-app
cd my-app
npx vize init
Nuxt:
npm create nuxt@latest my-app
cd my-app
npx vize init
init can add the Vite plugin or Nuxt module, Oxlint, vize fmt, vize check, and a VS Code
recommendation. If you already have Vite+, run
vpx vize init instead.
Migration
For an existing Vite, Vite+, or Nuxt project, preview the plan, then apply it:
npx vize init --dry-run
npx vize init
init is idempotent and lets you choose surfaces. Existing vize.config.* is left as-is. A second
run adds no duplicate plugin, script, or dependency. The first run may still add vize:* scripts
and update a plain vite.config.* or nuxt.config.*.
Non-interactive:
npx vize init --yes --lint --bundler --fmt --typecheck --editor
If you only want the compiler, use the drop-in swap above. Custom vue({ ... }) options and unusual
Vite configs are not rewritten automatically. See Project Setup.
Vize is in its Real World Testing phase: fix requests and PRs are very welcome, and we are looking for reasonably large Vue projects to use as test beds.
Benchmarks
One committed artifact supplies the README and every locale. File counts are stated per row.
Actions · f9cc50ee2e2f · JSON
Type-check ratios compare Vize with vue-tsc, the type checker Vue projects run today. vue-tsc drives the JavaScript TypeScript compiler while Vize drives native tsgo, so the ratio covers the whole toolchain rather than the Vue layer alone; the per-engine-class tables in the full snapshot rank same-engine tools against each other to isolate that layer. Each timed invocation passes diagnostic-work validation. Diagnostic coverage differs between tools; these ratios do not prove accuracy parity or a performance improvement over an earlier Vize version. Rejected comparators have no published timing or rank.
Nuxt measures the entire build pipeline, not isolated SFC compilation. Most build work is shared by both variants. Its ratio is 0.95x; a ratio below 1 means Vize was slower in this run.
See the Blacksmith benchmark snapshot for per-variant timings, diagnostic counts, rejected measurements and methodology.
Backend: native TypeScript engine ready at /home/runner/_work/vize/vize/node_modules/@typescript/typescript-linux-x64/lib/tsc. Planted-diagnostic gating for the type-check rows lives in tools/benchmarks/scripts/check-gate.mjs (.github/workflows/check-bench.yml).
Credits
This project draws inspiration from Volar.js, vuejs/language-tools, eslint-plugin-vue, eslint-plugin-vuejs-accessibility, Lightning CSS, Storybook, and OXC.
Special thanks to:
- Blacksmith for sponsoring high-performance CI/CD runners and Testbox infrastructure for frequent benchmarks and real-project compatibility checks.
- Mates Inc. for allowing ubugeeei, its employee, to dedicate discretionary work time to OSS and for adopting Vize in the build for the company's engineering website.
- Anthropic, through Claude for Open Source, for supporting Vize's ongoing open-source development.
- OpenAI Codex for Open Source for past support of Vize's open-source development. That support ended in September 2026.
- dmnlk for sustained code contributions and performance improvements, especially to Canon's type checker. As a Vize committer, dmnlk is entrusted with write access to the repository. Thank you for helping develop and maintain Vize.
- かっこかり for continuously testing Vize's compiler and Vite Plugin on Misskey (~103k lines of Vue across 586 SFCs), with timely reports as the implementation changed (report).
- ushironoko for compiler, linter, and CLI fix reports, reference implementations, and reproduction repositories.
- dannote for bringing Vize into the Elixir community through Volt, an Elixir-native frontend toolchain built on Vize, and for reporting missing pieces and sending PRs as Volt adopted Vize as a foundation.
- n13u and
#frontend_phpcon_dofor persistently reporting fix cases while building a Nuxt-based conference website with Vize, then carrying that validation all the way to production adoption (report, write-up). - yamanoku for accessibility-focused feedback around Vize and for using the project in the Vue Fes Japan speaker-site migration documented in the v-tokyo Meetup #25 LT notes (write-up).
Vize is a personal project by ubugeeei, licensed under the MIT License and maintained as a non-commercial OSS effort. It is not owned by any specific company, is intended to remain open, and is not being built with a buyout in mind.
