4 phút đọc
ubugeeei-prod/vize: blazing fast Vue.js toolchain. compiler, linter, type checker, formatter, lsp, story syste – Repository ubugeeei-prod/vize. Mô tả: blazing fast Vue.js toolchain. compiler, linter, type checker, formatter, lsp, story system, editors. already 30k+ tests.. 924 stars, 54 forks, ngôn ngữ chính Rust, cập nhật 2026-11-07.
1. Repository làm gì?
High-Performance Vue.js Toolchain in Rust
/viːz/: Named after Vizier + Visor + Advisor, a wise tool that sees through your code.
Documentation ・ Playground ・ Sponsor
▶ Watch the Real World Testing PV
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.
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.
2. Dữ liệu và cấu trúc đáng chú ý
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.
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.
On a Vue 3 + Vite app, replace @vitejs/plugin-vue with @vizejs/vite-plugin. Your SFCs stay as they are.
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-check .vue files with TypeScript 7.1 or newer and Vize's content mapper. tsrs can run the same tsconfig.
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.
3. Khả năng ứng dụng và giới hạn
Create a Vue + Vite or Nuxt app first, then let vize init wire the toolchain.
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.
For an existing Vite, Vite+, or Nuxt project, preview the plan, then apply it:
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.*.
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.
One committed artifact supplies the README and every locale. File counts are stated per row.
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.
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.
Số liệu repository có thể thay đổi; nên mở liên kết nguồn để kiểm tra README, giấy phép và trạng thái phát hành.
Nguồn tham khảo: Xem bài gốc
