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.

referencetextarea-no-interpolation.md

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

Textarea Interpolation is One-Way Only - Use v-model for Two-Way Binding

Impact: HIGH - Interpolation in textarea ({{ text }}) provides one-way binding only - it displays the initial value but user input does NOT update the ref. This creates a confusing disconnect where the textarea shows content but edits are silently lost.

Unlike v-model which provides two-way binding, interpolation only renders the initial ref value into the textarea. When users type, the ref remains unchanged, making form submissions return stale data. Always use v-model for two-way binding in textareas.

Task Checklist

  • Never use interpolation inside textarea tags
  • Always use v-model for textarea two-way binding
  • Search codebase for <textarea>{{ patterns that may be silently broken
  • Add linting rules to catch this pattern if possible

Incorrect:

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

const message = ref('Hello World')
</script>

<template>
  <!-- WRONG: One-way binding only! Shows initial value but edits don't update ref -->
  <textarea>{{ message }}</textarea>

  <!-- Also WRONG: User can type but changes are lost -->
  <textarea>{{ userBio }}</textarea>

  <!-- The textarea displays content but ref never updates -->
</template>

Correct:

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

const message = ref('Hello World')
</script>

<template>
  <!-- CORRECT: Use v-model for textarea -->
  <textarea v-model="message"></textarea>

  <!-- For read-only display, still use v-model or :value -->
  <textarea v-model="message" readonly></textarea>

  <!-- Or one-way binding with :value -->
  <textarea :value="message" readonly></textarea>
</template>
<!-- With placeholder and other attributes -->
<textarea
  v-model="message"
  placeholder="Enter your message..."
  rows="5"
  maxlength="500"
></textarea>

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.