Vue · props
Reports props a component declares but never reads in its script, inline template, or style v-bind(), using eslint-plugin-vue no-unused-properties limited to props. Files that pass the whole props object to code eslint cannot follow, such as useVModel(props) or reactiveOmit(props, 'class'), and files with src or non-HTML templates are skipped. It also keeps an unread prop that stops a fallthrough attribute: when inheritAttrs is on and the template has one root, a prop named like a global attribute or an attribute of that root element, such as title or alt, or typed as an object, array or function, would otherwise land on the root. Components in components/content/ and Prose components are skipped, since Markdown passes them every attribute an author writes. Single-file only: it does not check whether callers pass a prop. Strict Preset only.
vite-doctor/vuepropswarnNo fix
Why it happens
A declared prop the component never reads is dead contract. Callers can pass it and nothing changes, and readers assume it does something. It is usually left behind when a refactor moved or dropped its use.
Fix
Remove the prop from the props declaration and from the parents that pass it, or restore the read the component lost. Once a prop is no longer declared, a value parents still pass falls through to the root element as an attribute; if the declaration exists to stop that, keep it and suppress the diagnostic with that reason.
Example
Remove a prop left behind by a refactor
Before
<script setup lang="ts">
const props = defineProps<{ title: string; legacySize?: string }>()
</script>
<template>
<h1>{{ props.title }}</h1>
</template>
After
<script setup lang="ts">
const props = defineProps<{ title: string }>()
</script>
<template>
<h1>{{ props.title }}</h1>
</template>
Verify the fix
Run only this rule after editing so the report stays focused on the diagnostic you are closing:
pnpm vite-doctor . --framework vue --extends auto,vue/strict --rules vue/props/no-unused-props