Ecosystem rules

Follow each rule for purpose, severity, scope, configuration, and Bad/Good examples. The complete catalogue keeps all examples and current support boundaries on one page.

Configure lint.vize.rules and run vp run lint with the Vite+ helper. Check each page for type-aware, filename, or additional-configuration prerequisites.

Rule	Examples	Purpose
`ecosystem/nuxt-prefer-nuxt-link`	Bad · Good	Prefer NuxtLink for internal application links
`ecosystem/pinia-prefer-store-to-refs`	Bad · Good	Prefer storeToRefs() when destructuring Pinia stores
`ecosystem/router-link-require-to`	Bad · Good	Require a `to` target on RouterLink and NuxtLink components
`ecosystem/void-link-require-href`	Bad · Good	Require `href` on Void Vue Link components
`ecosystem/void-link-valid-method`	Bad · Good	Validate static Void Vue Link method props
`ecosystem/vue-i18n-no-missing-key`	Bad · Good	Report static vue-i18n keys that are absent from local SFC messages
`ecosystem/vue-router-prefer-named-link`	Bad · Good	Prefer named route objects over static path strings in RouterLink
`ecosystem/vue-router-prefer-named-push`	Bad · Good	Prefer named route objects for Vue Router programmatic navigation
`ecosystem/vue-test-utils-no-html-snapshot`	Bad · Good	Avoid snapshotting wrapper.html() in Vue Test Utils tests
`nuxt/no-nuxt-config-test-key`	Bad · Good	Disallow setting `test` key in Nuxt config
`nuxt/no-page-meta-runtime-values`	Bad · Good	Disallow runtime context values inside `definePageMeta` at the eager level, which is extracted into a separate chunk at build time and runs before component setup
`nuxt/nuxt-config-keys-order`	Bad · Good	Prefer recommended order of Nuxt config properties
`nuxt/prefer-import-meta`	Bad · Good	Prefer using `import.meta.` over `process.`

All rules · Rule Options · ESLint migration map · Project checks

For the four typed Vue Router diagnostics, see the complete project examples.