Rules

Vize diagnostics are documented as rules, not as one large matrix. Each rule page keeps the detection behavior close to the Bad/Good examples so the reference can be read like an ESLint rule manual.

Pages

• Vue rules: SFC template structure, Vue directives, component conventions, and single-file Vue correctness checks.

• Type and script rules: TypeScript checker-backed diagnostics and Vapor script restrictions.

• HTML rules: HTML validity and semantic markup checks.

• Accessibility rules: ARIA, keyboard interaction, labels, landmarks, and accessible media checks.

• SSR rules: server rendering and hydration hazards.

• Vapor rules: Vapor-only template constraints.

• Ecosystem rules: preset-backed checks for Nuxt, Vue Router, Pinia, vue-i18n, Vue Test Utils, and Void Vue.

• Musea and CSS rules: Musea art-block checks and style diagnostics.

• Cross-file rules: project-graph diagnostics emitted by vize lint --cross-file.

Presets

essential contains correctness rules that should almost always be enabled. happy-path adds practical hygiene checks for day-to-day Vue development. ecosystem adds Vue Router, Vue I18n, Pinia, Vue Test Utils, Nuxt, and Void Vue checks. nuxt includes Nuxt-oriented SSR expectations and Vapor expectations. opinionated is the broadest built-in preset.

incremental starts empty. Use it when a host wants to opt into specific rules without inheriting a larger preset.

Type-Aware Configuration

Rules that need semantic information read the TypeScript project through tsconfig.json. Prefer putting shared environment names in compilerOptions.types or project references instead of keeping a separate globals list in Vize config.