ESLint rule migration map

The committed ESLint mapping records 252 rule IDs: 123 mapped, 2 intentional divergences, and 127 unimplemented. A mapped ID identifies a Vize rule; it does not guarantee identical options, findings, fixes, or coverage.

Enable Vize rules under lint.vize.rules in the Vite+ configuration. Keep JS/TS rules handled by Oxlint in lint.rules. Do not copy an ESLint option tuple directly: Vize severity and typed ruleOptions are separate.

 import vue from "eslint-plugin-vue";
 export default [{ plugins: { vue }, rules: { "vue/attributes-order": "warn" } }];
 import { defineConfig } from "@vizejs/vite-plugin/vite-plus";
 export default defineConfig({
   lint: { vize: { rules: { "vue/attribute-order": "warn" } } },
 });

Remove only the overlapping Vue rule after checking the linked Bad/Good examples. Run vp run lint; if an existing package script occupies that task name, the generated task is vp run vize:lint. Explicit task configuration takes precedence.

vue/component-definition-name-casing has a deliberate scope difference: Vize checks the SFC filename, while ESLint checks the component definition name. The mapping below retains this distinction.

For option conversion, see Rule Options and props destructuring modes. Unsupported rows must stay with an existing checker until a supported replacement is verified.

Committed mapping and capture identity