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.

referencedynamic-argument-constraints.md

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

Dynamic Directive Arguments Have Syntax Constraints

Impact: MEDIUM - Dynamic directive arguments (e.g., :[attributeName], @[eventName]) have value and syntax constraints that can cause silent failures. In-DOM templates also have case sensitivity issues with browsers lowercasing attribute names.

Dynamic arguments allow runtime determination of which attribute or event to bind, but they have restrictions that differ from static arguments.

Task Checklist

  • Ensure dynamic arguments evaluate to strings or null
  • Avoid spaces and quotes inside dynamic argument brackets
  • Use computed properties for complex dynamic argument expressions
  • In in-DOM templates, use lowercase attribute names or switch to SFCs
  • Use null to explicitly remove a binding

Incorrect:

<template>
  <!-- ERROR: Spaces and quotes not allowed in dynamic arguments -->
  <a :[' foo' + bar]="value">Link</a>
  <a :["data-" + name]="value">Link</a>

  <!-- WARNING: Non-string values (except null) trigger warnings -->
  <a :[123]="value">Link</a>
  <a :[someObject]="value">Link</a>

  <!-- BUG in in-DOM templates: Browsers lowercase attribute names -->
  <!-- This becomes :[someattr] which won't match someAttr -->
  <a :[someAttr]="url">Link</a>
</template>

<script setup>
// If component expects someAttr but browser lowercases to someattr
// the binding silently fails
const someAttr = 'href'
</script>

Correct:

<template>
  <!-- OK: Simple variable reference -->
  <a :[attributeName]="url">Link</a>

  <!-- OK: Use computed property for complex expressions -->
  <a :[dynamicAttr]="value">Link</a>

  <!-- OK: null removes the binding -->
  <button :[disabledAttr]="isDisabled">Submit</button>

  <!-- OK: Dynamic event names -->
  <button @[eventName]="handler">Click</button>

  <!-- OK: In SFCs, case is preserved -->
  <a :[someAttr]="url">Link</a>
</template>

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

// Simple string variable
const attributeName = ref('href')
const url = ref('https://vuejs.org')

// Complex expression via computed property
const prefix = ref('data')
const name = ref('id')
const dynamicAttr = computed(() => `${prefix.value}-${name.value}`)

// Conditional binding with null
const isDisabled = ref(false)
const disabledAttr = computed(() => isDisabled.value ? 'disabled' : null)

// Dynamic events
const useTouch = ref(false)
const eventName = computed(() => useTouch.value ? 'touchstart' : 'click')

function handler() {
  console.log('Event triggered')
}
</script>

In-DOM Template Workaround

When writing templates directly in HTML (not SFCs), use lowercase:

<!-- In-DOM template (index.html) -->
<div id="app">
  <!-- Use lowercase to avoid browser issues -->
  <a :[attrname]="url">Link</a>
</div>

<script type="module">
import { createApp, ref } from 'vue'

createApp({
  setup() {
    // Match the lowercase used in template
    const attrname = ref('href')
    const url = ref('https://vuejs.org')
    return { attrname, url }
  }
}).mount('#app')
</script>

SFC vs In-DOM Templates

Feature SFC (.vue files) In-DOM (HTML)
Case sensitivity Preserved Lowercased by browser
Dynamic arguments Full support Lowercase only
Recommendation Preferred Use for progressive enhancement

Valid Dynamic Argument Values

<script setup>
// String values - OK
const attr1 = 'href'
const attr2 = 'data-custom'

// null - OK (removes binding)
const attr3 = null

// undefined - OK (removes binding)
const attr4 = undefined

// Numbers, objects, arrays - WARNING
const attr5 = 123        // Warning: should be string
const attr6 = { foo: 1 } // Warning: should be string
</script>

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.