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.

referenceinheritattrs-false-for-wrapper-components.md

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

Use inheritAttrs: false for Wrapper Components

Rule

When building wrapper components where attributes should be applied to an inner element instead of the root element, always set inheritAttrs: false and explicitly bind $attrs to the target element.

Why This Matters

  • By default, Vue applies all non-prop attributes to the root element
  • Wrapper components often have a non-semantic root (div wrapper, label wrapper)
  • Attributes like id, aria-*, data-*, and event listeners should target the functional element
  • Without inheritAttrs: false, accessibility and functionality can break

Bad Code

<!-- BaseInput.vue - WRONG: attrs go to wrapper div, not input -->
<template>
  <div class="input-wrapper">
    <label>{{ label }}</label>
    <input type="text" />
  </div>
</template>

<script setup>
defineProps(['label'])
</script>

<!-- Parent usage -->
<BaseInput
  id="email"
  placeholder="Enter email"
  aria-describedby="email-help"
  @focus="handleFocus"
/>

<!--
  RESULT: All attrs go to the wrapper div!
  <div class="input-wrapper" id="email" placeholder="Enter email" ...>
    <label>...</label>
    <input type="text" />  <!-- No id, placeholder, or aria! -->
  </div>
-->

Good Code

<!-- BaseInput.vue - CORRECT: attrs bound to input element -->
<script setup>
defineProps(['label'])

defineOptions({
  inheritAttrs: false
})
</script>

<template>
  <div class="input-wrapper">
    <label>{{ label }}</label>
    <input type="text" v-bind="$attrs" />
  </div>
</template>

<!-- Parent usage -->
<BaseInput
  id="email"
  placeholder="Enter email"
  aria-describedby="email-help"
  @focus="handleFocus"
/>

<!--
  RESULT: Attrs correctly applied to input
  <div class="input-wrapper">
    <label>...</label>
    <input type="text" id="email" placeholder="Enter email"
           aria-describedby="email-help" />
  </div>
-->

Setting inheritAttrs in Different Syntaxes

Script Setup (Vue 3.3+)

<script setup>
defineOptions({
  inheritAttrs: false
})
</script>

Script Setup (Before Vue 3.3)

<script>
export default {
  inheritAttrs: false
}
</script>

<script setup>
// Your setup code here
</script>

Options API

<script>
export default {
  inheritAttrs: false,
  // other options...
}
</script>

Common Wrapper Component Patterns

Form Input Wrapper

<script setup>
import { useAttrs, computed } from 'vue'

defineProps({
  label: String,
  error: String
})

defineOptions({
  inheritAttrs: false
})

const attrs = useAttrs()

// Separate class/style for wrapper vs input
const inputAttrs = computed(() => {
  const { class: _, style: __, ...rest } = attrs
  return rest
})
</script>

<template>
  <div class="form-field" :class="{ 'has-error': error }">
    <label v-if="label">{{ label }}</label>
    <input v-bind="inputAttrs" />
    <span v-if="error" class="error">{{ error }}</span>
  </div>
</template>

Button with Icon Wrapper

<script setup>
defineProps({
  icon: String,
  iconPosition: {
    type: String,
    default: 'left'
  }
})

defineOptions({
  inheritAttrs: false
})
</script>

<template>
  <button class="icon-button" v-bind="$attrs">
    <span v-if="icon && iconPosition === 'left'" class="icon">{{ icon }}</span>
    <slot />
    <span v-if="icon && iconPosition === 'right'" class="icon">{{ icon }}</span>
  </button>
</template>

Link Wrapper Component

<script setup>
defineProps({
  to: String,
  external: Boolean
})

defineOptions({
  inheritAttrs: false
})
</script>

<template>
  <a
    v-if="external"
    :href="to"
    target="_blank"
    rel="noopener noreferrer"
    v-bind="$attrs"
  >
    <slot />
  </a>
  <router-link v-else :to="to" v-bind="$attrs">
    <slot />
  </router-link>
</template>

When NOT to Use inheritAttrs: false

  • Simple components with a single semantic root element
  • Components where the root element should receive all attributes
  • Components that don't wrap other functional elements
<!-- SimpleCard.vue - No need for inheritAttrs: false -->
<template>
  <article class="card">
    <slot />
  </article>
</template>
<!-- Passing class, id, or data-* to the root article is fine -->

References

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.