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.

referencewatch-async-creation-memory-leak.md

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

Watchers Created Asynchronously Must Be Manually Stopped

Impact: HIGH - Watchers created inside async callbacks (setTimeout, Promise.then, async/await) are not automatically bound to the component instance. They continue running after the component unmounts, causing memory leaks and errors.

Always manually stop watchers that are created asynchronously, or restructure your code to create watchers synchronously with conditional logic.

Task Checklist

  • Create watchers synchronously in setup() or lifecycle hooks when possible
  • If async creation is unavoidable, store and call the unwatch function
  • Use onUnmounted to clean up async-created watchers
  • Consider using conditional logic inside a sync watcher instead
  • Watch for this pattern in setTimeout, Promise callbacks, and after await

Incorrect:

<script setup>
import { ref, watch, watchEffect, onMounted } from 'vue'

const data = ref(null)

// BAD: Watcher created in setTimeout won't auto-stop
onMounted(() => {
  setTimeout(() => {
    watchEffect(() => {
      console.log(data.value)  // Keeps running after unmount!
    })
  }, 1000)
})

// BAD: Watcher created after await won't auto-stop
onMounted(async () => {
  await loadInitialData()

  // This watcher is NOT bound to component lifecycle
  watch(data, (newVal) => {
    processData(newVal)  // Memory leak!
  })
})

// BAD: Watcher in Promise callback
fetch('/api/config').then(() => {
  watch(data, () => {
    // Leaks memory!
  })
})
</script>

Correct:

<script setup>
import { ref, watch, watchEffect, onMounted, onUnmounted } from 'vue'

const data = ref(null)
const isDataLoaded = ref(false)
let asyncWatcherCleanup = null

// CORRECT: Synchronous watcher with conditional logic
watch(
  data,
  (newVal) => {
    if (isDataLoaded.value && newVal) {
      processData(newVal)
    }
  }
)

onMounted(async () => {
  await loadInitialData()
  isDataLoaded.value = true
})

// CORRECT: Manual cleanup for async-created watcher
onMounted(() => {
  setTimeout(() => {
    const unwatch = watchEffect(() => {
      console.log(data.value)
    })

    // Store for cleanup
    asyncWatcherCleanup = unwatch
  }, 1000)
})

onUnmounted(() => {
  // Clean up async watcher
  if (asyncWatcherCleanup) {
    asyncWatcherCleanup()
  }
})
</script>

Preferred Pattern: Conditional Watch Logic

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

const config = ref(null)
const userData = ref(null)

// BEST: Create watcher synchronously, handle async condition inside
watch(
  userData,
  (newData) => {
    // Only process when config is loaded
    if (config.value && newData) {
      applyUserSettings(config.value, newData)
    }
  }
)

onMounted(async () => {
  config.value = await fetchConfig()
  // Watcher will start processing once config is loaded
})
</script>

Using watchEffect with Conditional Logic

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

const apiData = ref(null)
const isReady = ref(false)

// GOOD: Synchronous watchEffect with condition
watchEffect(() => {
  if (isReady.value && apiData.value) {
    // This pattern avoids async watcher creation
    doSomethingWithData(apiData.value)
  }
})

onMounted(async () => {
  apiData.value = await fetchData()
  isReady.value = true
})
</script>

Tracking Multiple Async Watchers

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

const unwatchers = []

function createDynamicWatcher(source, callback) {
  const unwatch = watch(source, callback)
  unwatchers.push(unwatch)
  return unwatch
}

// Clean up all dynamic watchers
onUnmounted(() => {
  unwatchers.forEach(unwatch => unwatch())
})
</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.