Vize

[!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.

Runner	Measured	Runs	Warmups
blacksmith-32vcpu-ubuntu-2404 (32 CPU)	2026-11-03T16:43:39.549Z	5	1

Actions · 3d9c82f75c2a · JSON

Surface	Files	Existing tool	Existing	Vize	Speedup
SFC compile	15,000	@vue/compiler-sfc	16.50s	297.9ms	55.4×
Lint	15,000	eslint-plugin-vue	99.32s	499.8ms	198.7×
Format	15,000	Prettier	141.76s	844.7ms	167.8×
Type check	500	vue-tsc	6.50s	573.5ms	11.3×
Vite build	1,000	@vitejs/plugin-vue	1.48s	448.9ms	3.3×
Nuxt build	500	Nuxt compiler	3.66s	3.32s	1.1×

Type-check rows on the 500-SFC corpus: each tool at its fastest measured setting (the full checker-count matrix is in the snapshot). Each row reports every planted diagnostic before it is timed. Warm is the median of the measured runs, Cold is the row's first timed run, CPU is user+sys time of the whole process tree (mapper processes included), and Peak RSS is the largest single process.

This is the beginning of the README. Read the rest at the original. Read the full README ↗