Current Direction
One of the biggest recent shifts in Vize is native type checking. vize check and the editor-facing type-check pipeline are moving onto vize_canon plus corsa-bind, which lets Vize keep Vue virtual files and TypeScript project diagnostics on a native path for longer.
That matters for more than raw speed. It gives Vize a tighter loop between template analysis, diagnostics, navigation, and future editor features, while reducing the amount of work that has to bounce back through a JavaScript-hosted compiler process. The fidelity story is still catching up, but this is the direction the toolchain is clearly heading.
The same direction applies to linting and Musea. Static analysis starts with the parser and Croquis semantic model, then feeds Patina lint rules, Canon virtual TypeScript, compiler decisions, editor diagnostics, and component gallery metadata. The practical workflow is documented in Static Analysis, with config details in Configuration. The concrete rule and diagnostic catalog is in Rules.
Author

ubugeeei is a software engineer based in Tokyo, working across Vue, Rust, design, and language tooling.
He is part of the Vue.js Core Team, Vue.js Japan User Group Core Staff, a Vite+ Core Contributor, and Chief Engineer at mates-dev.
He is also the creator of chibivue, Vize, and Ox Content.
GitHub: github.com/ubugeeei
X (Twitter): @ubugeeei
Blog: wtrclred.io
chibivue.land: chibivue.land
Sponsor
Vize is a free and open-source project licensed under MIT. Developing and maintaining a full toolchain — compiler, linter, formatter, type checker, LSP, component gallery, and WASM bindings — is a significant effort that requires sustained focus and dedication.
If Vize saves you time, improves your development experience, or you believe in the vision of a high-performance Vue.js toolchain, please consider sponsoring the project:
Your support helps fund continued development, infrastructure costs, and ensures Vize remains free for everyone. Every contribution — no matter the size — makes a real difference.