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.

referencetemplate-ref-unwrapping-top-level.md

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

Template Ref Unwrapping Only Works for Top-Level Properties

Impact: MEDIUM - Vue only auto-unwraps refs that are top-level properties in the template render context. Nested refs (refs inside objects) are NOT unwrapped in expressions, causing [object Object] rendering or calculation errors.

This caveat trips up developers when they store refs inside reactive objects or plain objects and try to use them in template expressions like {{ object.count + 1 }}.

Task Checklist

  • Keep refs at the top level of your setup return or script setup
  • Destructure nested refs to top-level variables before using in expressions
  • Be aware that text interpolation {{ object.ref }} DOES unwrap, but expressions {{ object.ref + 1 }} do NOT
  • Consider restructuring data to avoid nested refs in templates

Incorrect:

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

const count = ref(0)
const object = { id: ref(1) }
</script>

<template>
  <!-- WRONG: Nested ref in expression - does NOT unwrap -->
  <p>ID + 1 = {{ object.id + 1 }}</p>
  <!-- Renders: "ID + 1 = [object Object]1" -->

  <!-- Surprisingly, plain interpolation DOES work -->
  <p>ID = {{ object.id }}</p>
  <!-- Renders: "ID = 1" (unwrapped because it's the final expression) -->
</template>

Correct:

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

const count = ref(0)
const object = { id: ref(1) }

// SOLUTION 1: Destructure to top-level
const { id } = object
</script>

<template>
  <!-- CORRECT: Top-level ref unwraps in all expressions -->
  <p>Count + 1 = {{ count + 1 }}</p>
  <!-- Renders: "Count + 1 = 1" -->

  <!-- CORRECT: Destructured ref is now top-level -->
  <p>ID + 1 = {{ id + 1 }}</p>
  <!-- Renders: "ID + 1 = 2" -->
</template>
<script setup>
import { ref, computed } from 'vue'

const object = { id: ref(1) }

// SOLUTION 2: Use computed for derived values
const idPlusOne = computed(() => object.id.value + 1)
</script>

<template>
  <!-- CORRECT: Computed handles the .value access -->
  <p>ID + 1 = {{ idPlusOne }}</p>
</template>
<script setup>
import { reactive } from 'vue'

// SOLUTION 3: Use reactive object instead (refs inside reactive auto-unwrap)
const object = reactive({ id: 1 })
</script>

<template>
  <!-- CORRECT: Plain reactive property works in expressions -->
  <p>ID + 1 = {{ object.id + 1 }}</p>
</template>
// WHY this happens:
// - Template compilation only adds .value to top-level identifiers
// - {{ count + 1 }} compiles to: count.value + 1
// - {{ object.id + 1 }} compiles to: object.id + 1 (no .value added!)
// - Plain {{ object.id }} has special handling for display purposes

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.