Vize
vize:croquis/cf/undefined-slot
A parent fills a slot the child does not expose.
Default severity: Not emitted
Applies to: Analyzed component graph and the supported facts described below
Automatic fix: None; review related files and apply the repair
Options: No per-code options; supported CLI findings accept severity overrides
This is a published diagnostic contract without a current producer. The Bad/Good scenario below explains the risk and repair; no flag currently makes this code trigger.
Shared project files
Use these unchanged files in both Bad and Good. Install the imported packages in the project: Vue, plus vue-router or Pinia where shown. Follow any version-specific support note. The entry root makes the component relationship explicit.
main.ts
import { createApp } from 'vue';
import App from './App.vue';
createApp(App).mount('#app');
index.html
<!doctype html>
<html lang="en"><head><meta charset="UTF-8"><title>Contract scenario</title></head>
<body><div id="app"></div><script type="module" src="/main.ts"></script></body></html>
Card.vue
<script setup lang="ts">
defineSlots<{ header(): unknown }>();
</script>
<template>
<article><header><slot name="header" /></header></article>
</template>
Bad
App supplies a footer slot, but Card declares and renders only header. The supplied Notice content has no matching slot outlet in this child.
App.vue
<script setup lang="ts">
import Card from './Card.vue';
</script>
<template>
<Card><template #footer>Notice</template></Card>
</template>
Good
App supplies header, matching both the child’s typed slot declaration and its rendered outlet, so Notice appears there.
App.vue
<script setup lang="ts">
import Card from './Card.vue';
</script>
<template>
<Card><template #header>Notice</template></Card>
</template>
The Good files demonstrate the change described above; other diagnostics can still apply to the complete project.