All skills
vuejs-ai avatar

/vue-debug-guides

@a5fc891 official
by Vue AIvuejs-ai/skills2.9k stars
167

Vue 3 debugging and error handling for runtime errors, warnings, async failures, and SSR/hydration issues. Use when diagnosing or fixing Vue issues.

Use this Skill: https://skilld.dev/gh/vuejs-ai/skills/vue-debug-guides

This session only. Nothing lands on disk.

referenceslot-forwarding-to-child-components.md

≈1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Forward Slots to Child Components Correctly

Impact: MEDIUM - When creating wrapper components that enhance or extend other components, you need to forward slots from the parent to the wrapped child. Without proper slot forwarding, consumers of your wrapper cannot customize the inner component's slots.

Task Checklist

  • Use v-for with $slots to iterate over all provided slots
  • Use dynamic slot names with v-slot:[slotName]
  • Pass slot props through with v-bind="slotProps"
  • Handle cases where slotProps might be undefined

Basic Slot Forwarding Pattern:

<!-- EnhancedButton.vue - Wrapper component -->
<script setup>
import BaseButton from './BaseButton.vue'
</script>

<template>
  <div class="button-wrapper">
    <BaseButton v-bind="$attrs">
      <!-- Forward all slots to BaseButton -->
      <template v-for="(_, slotName) in $slots" v-slot:[slotName]="slotProps">
        <slot :name="slotName" v-bind="slotProps ?? {}" />
      </template>
    </BaseButton>
  </div>
</template>

Usage:

<script setup>
import EnhancedButton from './EnhancedButton.vue'
</script>

<template>
  <!-- Slots pass through to BaseButton -->
  <EnhancedButton>
    <template #icon>
      <IconCheck />
    </template>
    <template #default>
      Click me
    </template>
  </EnhancedButton>
</template>

Handling Scoped Slots

When the child component provides slot props, you must forward them:

<!-- DataTableWrapper.vue -->
<script setup>
import DataTable from './DataTable.vue'

const props = defineProps(['data'])
</script>

<template>
  <div class="table-container">
    <DataTable :items="data">
      <!-- Forward slots including scoped slot props -->
      <template v-for="(_, slotName) in $slots" v-slot:[slotName]="slotProps">
        <slot :name="slotName" v-bind="slotProps ?? {}" />
      </template>
    </DataTable>
  </div>
</template>
<!-- Consumer can use scoped slot props -->
<DataTableWrapper :data="users">
  <template #row="{ item, index }">
    <tr>
      <td>{{ index + 1 }}</td>
      <td>{{ item.name }}</td>
    </tr>
  </template>
</DataTableWrapper>

Alternative: Handling Undefined slotProps

Some scenarios require checking if slotProps exists:

<template>
  <ChildComponent>
    <template v-for="(_, name) in $slots" v-slot:[name]="slotProps">
      <!-- Handle both scoped and non-scoped slots -->
      <slot v-if="slotProps" :name="name" v-bind="slotProps" />
      <slot v-else :name="name" />
    </template>
  </ChildComponent>
</template>

Forwarding Specific Slots Only

If you only want to forward certain slots:

<template>
  <ChildComponent>
    <!-- Only forward header and footer slots -->
    <template v-if="$slots.header" #header="slotProps">
      <slot name="header" v-bind="slotProps ?? {}" />
    </template>

    <template v-if="$slots.footer" #footer="slotProps">
      <slot name="footer" v-bind="slotProps ?? {}" />
    </template>

    <!-- Default slot handled differently -->
    <slot />
  </ChildComponent>
</template>

Common Mistakes

Mistake Problem Solution
Not using v-bind="slotProps" Scoped slot data lost Always bind slotProps
Forgetting ?? {} or null check Error when slotProps undefined Add nullish coalescing
Static slot names in loop Only forwards one slot Use v-slot:[slotName] dynamic syntax
Missing v-for key warning Vue warning (non-critical) Keys not needed for slot functions

Reference

Source: SKILL.md on GitHub

1 warning17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    This skill is a comprehensive collection of educational debugging guides and best practices for Vue 3 developers. It contains no executable code or malicious instructions and focuses solely on diagnosing common runtime errors and performance issues.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    140/140 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at a5fc891. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Steadyupdated 8 months ago

README badge

README badge for vuejs-ai/skills/vue-debug-guides

Guides for diagnosing Vue 3 runtime errors, reactivity bugs, component lifecycle issues, and SSR hydration problems. Covers reactivity traps (refs, computed, watchers), component mechanics (props, emits, slots), templates (v-if, v-for, refs), forms (v-model), and composition API gotchas.

Generated from the current SKILL.md.

Does this cover Vue 2 or only Vue 3?
This skill is for Vue 3 only. It addresses Vue 3-specific debugging patterns like reactivity proxies, script setup, and defineEmits/defineProps.
Does this skill help with performance optimization?
No. This skill focuses on runtime errors, warnings, and behavioral bugs. For development best practices and optimization, use the separate `vue-best-practices` skill.
What kinds of issues does this cover?
Reactivity traps (refs, computed, watchers), component lifecycle bugs, template directives, form binding edge cases, SSR/hydration mismatches, slot scoping, and async-related failures.
Does this include debugging for Nuxt or other Vue frameworks?
No. This skill focuses on core Vue 3 runtime issues. Framework-specific bugs are outside its scope.

Generated from the current SKILL.md. These answers refresh after source changes.