`script/no-potential-component-option-typo`

Flag likely typos in Options API component option names

Default severity: error
Presets: essential, happy-path, ecosystem, nuxt, opinionated
Automatic fix: None; review the suggested change
Applies to: JS/TS scripts in Vue SFCs; examples show the relevant Options API or script setup form
Options: No rule-specific options. Severity and preset selection are configurable.

Configuration (Vite+)

import { defineConfig } from "@vizejs/vite-plugin/vite-plus";

export default defineConfig({
  lint: {
    vize: {
      "preset": "incremental",
      "rules": {
        "script/no-potential-component-option-typo": "error"
      }
    },
  },
});

vp run lint

Bad

The option is spelled method, one edit away from the recognized methods option; Vue would not treat it as the intended methods declaration.

<script lang="ts">
export default { method: { save() {} } };
</script>

Good

Changing the key to methods places save() under the recognized component option.

<script lang="ts">
export default { methods: { save() {} } };
</script>

Good avoids this rule's finding under the configuration above; other rules may still report diagnostics.

Implementation · All rules