All skills
hyf0 avatar

/vue-debug-guides

@a5fc891 official
by hyf0hyf0/vue-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/hyf0/vue-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

No alerts17d5 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 files scanned · No issues

  • 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 hyf0/vue-skills/vue-debug-guides

Guides for diagnosing and fixing Vue 3 runtime errors, reactivity bugs, async failures, and hydration issues across components, templates, watchers, forms, and lifecycle hooks. Covers specific failure modes like stale watchers, ref unwrapping edge cases, v-model sync problems, and SSR mismatches with concrete reference links for each issue.

Generated from the current SKILL.md.

Does this skill cover Vue 2?
No. This skill is specific to Vue 3 debugging and error handling.
What should I use for Vue development best practices instead of debugging?
The skill references a separate `vue-best-practices` skill for development best practices and common gotchas.
Does this cover SSR and hydration issues?
Yes. The skill includes guides for diagnosing and fixing SSR rendering differences and hydration bugs.
Can this help with async watcher and watchEffect problems?
Yes. The skill covers async operation stale data, dependency tracking after await, and proper flush timing for watchers.
Does this address v-model and form-related issues?
Yes. The skill includes guides for v-model initial values, textarea interpolation, IME composition, and custom checkbox form submission.

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