Vue Reactivity ref, reactive, computed, watch is an important Vue JS topic because it appears in real projects, debugging sessions, and interviews. Learn the meaning first, then connect it to a small working example so the rule does not stay abstract.
For this page, focus on what problem Vue Reactivity ref, reactive, computed, watch solves, where developers usually make mistakes, and how to verify the result. The audit note for this lesson was: under 650 content words; limited checklist/practice/mistake/FAQ notes .
A strong understanding of Vue Reactivity ref, reactive, computed, watch should include syntax, behavior, one realistic use case, one failure case, and one quick way to check your work with tools or output.
Vue Reactivity ref reactive computed watch should be studied as a practical Vue application development lesson, not as a label. Start by naming the input, the rule that changes the input, and the result a learner should be able to predict after reading the page.
In the vue-js > reactivity page, the notes should connect the definition with a working scenario, a mistake that beginners actually make, and the exact check that proves the fix. That makes the topic useful for coding, debugging, and interview revision.
Vue's reactivity system automatically tracks data dependencies and updates the DOM when data changes. In Vue 3's Composition API, you declare reactive state using ref() and reactive().
| API | Use for | Access value |
|---|---|---|
| ref() | Primitives (string, number, boolean) and any value | count.value in JS, {{ count }} in template |
| reactive() | Objects and arrays | state.name directly (no .value) |
| computed() | Derived values - auto-updates when deps change | Like ref - .value in JS |
| watch() | Side effects when data changes | Callback receives new/old value |
| watchEffect() | Auto-track dependencies, run immediately | No explicit deps needed |
<template>
<div>
<!-- ref values -->
<p>Count: {{ count }}</p>
<p>Name: {{ name }}</p>
<button @click="count++">+1</button>
<!-- reactive object -->
<p>{{ user.name }} ({{ user.age }})</p>
<button @click="user.age++">Birthday</button>
<!-- computed -->
<p>Full name: {{ fullName }}</p>
<p>Double: {{ double }}</p>
<p>Filtered: {{ filteredItems.length }} items</p>
</div>
</template>
<script setup>
import { ref, reactive, computed } from 'vue'
// ref - for primitives
const count = ref(0)
const name = ref('Alice')
// reactive - for objects
const user = reactive({
firstName: 'Alice',
lastName: 'Smith',
age: 25
})
const items = reactive([
{ id: 1, name: 'Apple', active: true },
{ id: 2, name: 'Banana', active: false },
{ id: 3, name: 'Cherry', active: true },
])
// computed - derived, cached, auto-updates
const fullName = computed(() => `${user.firstName} ${user.lastName}`)
const double = computed(() => count.value * 2)
const filteredItems = computed(() => items.filter(i => i.active))
// Writable computed
const firstName = ref('Alice')
const lastName = ref('Smith')
const fullNameWritable = computed({
get: () => `${firstName.value} ${lastName.value}`,
set: (val) => {
const parts = val.split(' ')
firstName.value = parts[0]
lastName.value = parts[1] || ''
}
})
</script>
<template>
<div>
<input v-model="searchQuery" placeholder="Search..." />
<p>Results: {{ results.length }}</p>
<p>User: {{ user.name }}</p>
</div>
</template>
<script setup>
import { ref, reactive, watch, watchEffect } from 'vue'
const searchQuery = ref('')
const results = ref([])
const user = reactive({ name: 'Alice', age: 25 })
// watch - explicit source, runs when it changes
watch(searchQuery, async (newVal, oldVal) => {
console.log(`Changed from "${oldVal}" to "${newVal}"`)
if (newVal.length > 2) {
results.value = await fetchResults(newVal)
}
})
// watch with options
watch(searchQuery, (newVal) => {
console.log('Debounced search:', newVal)
}, {
immediate: true, // run immediately on mount
deep: false // don't watch nested properties
})
// Watch reactive object - need deep: true for nested changes
watch(user, (newUser) => {
console.log('User changed:', newUser)
}, { deep: true })
// Watch specific property of reactive object
watch(() => user.age, (newAge) => {
console.log('Age changed to:', newAge)
})
// watchEffect - auto-tracks dependencies, runs immediately
watchEffect(() => {
// Automatically tracks searchQuery.value
console.log('Query is now:', searchQuery.value)
document.title = `Search: ${searchQuery.value}`
})
// Stop a watcher
const stop = watchEffect(() => { /* ... */ })
// stop() // call to stop watching
async function fetchResults(query) {
const res = await fetch(`/api/search?q=${query}`)
return res.json()
}
</script>
Understanding Reactivity is not just about syntax. In production applications, this topic directly affects maintainability, debugging speed, and team collaboration. Focus on readability, small reusable patterns, and predictable state flow when implementing Reactivity.
A practical approach is to first implement the simplest working version, then refactor into reusable pieces (components/composables/stores) only when duplication appears. This helps keep your Vue codebase clean while avoiding over-engineering.
When studying Vue Reactivity ref, reactive, computed, watch, separate three things: the concept, the syntax, and the situation where it is useful. This prevents the lesson from becoming a list of commands with no practical meaning.
In Vue JS, Vue Reactivity ref, reactive, computed, watch becomes easier when you build a tiny example first, then increase complexity. Add one realistic input, one invalid or boundary input, and one explanation of why the result changes.
const state = { topic: "Vue Reactivity ref reactive computed watch", ready: true };
if (state.ready) {
console.log(state.topic + ": render or run the normal path");
}
const response = null;
const message = response?.message ?? "Vue Reactivity ref reactive computed watch: show a clear fallback";
console.log(message);
Memorizing Vue Reactivity ref reactive computed watch without the situation where it is useful.
Connect Vue Reactivity ref reactive computed watch to a concrete Vue application development task.
Testing Vue Reactivity ref reactive computed watch only with the perfect input.
Include empty, missing, duplicate, incompatible, or failed cases when relevant.
Changing code before reading the visible symptom or error message.
Inspect the output, state, configuration, or stack trace connected to Vue Reactivity ref reactive computed watch.
Memorizing Vue Reactivity ref reactive computed watch without the situation where it is useful.
Connect Vue Reactivity ref reactive computed watch to a concrete Vue application development task.
The common mistake is memorizing syntax without understanding when the behavior changes or fails.
Remember the problem it solves in Vue application development, then attach the syntax or steps to that problem.
You can predict the result of a small example, explain a failure case, and choose it over a nearby alternative for a clear reason.
They often copy the syntax but skip the state, input, dependency, selector, route, type, or configuration that controls the behavior.
Explore 500+ free tutorials across 20+ languages and frameworks.