Debounced watchers pattern in Vue - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when the watched value changes rapidly in this debounced watcher?

Consider a Vue 3 component using a debounced watcher on a reactive property. If the property changes multiple times quickly, what will the watcher callback do?

Vue

<script setup>
import { ref, watch } from 'vue'
import { debounce } from 'lodash-es'

const searchTerm = ref('')

const debouncedSearch = debounce((newVal) => {
  console.log('Search for:', newVal)
}, 300)

watch(searchTerm, (newVal) => {
  debouncedSearch(newVal)
})
</script>

A The watcher callback runs only once, 300ms after the last change stops.

B The watcher callback runs immediately on every change without delay.

C The watcher callback runs multiple times, each delayed by 300ms from the previous.

D The watcher callback never runs because debounce blocks it.

💡 Hint

Think about how debounce delays function calls until changes stop.

Debounce delays the execution of the callback until 300ms have passed without new calls. Rapid changes reset the timer, so only the last change triggers the callback after the delay.

📝 Syntax

intermediate

Which option correctly implements a debounced watcher in Vue 3 Composition API?

Select the code snippet that correctly sets up a debounced watcher on a reactive property named 'query' using lodash debounce.

A const debounced = debounce((val) => console.log(val), 200); watch(query, debounced)

B watch(query, (val) => { debounce(() => console.log(val), 200)() })

C watch(query, debounce((val) => { console.log(val) }, 200))

D watch(debounce(query, 200), (val) => console.log(val))

💡 Hint

Debounce wraps the callback, not the reactive source.

You create a debounced function first, then pass it as the watcher callback. Wrapping the source or calling debounce inside the watcher callback is incorrect.

🔧 Debug

advanced

Why does this debounced watcher log stale values?

This Vue 3 component uses a debounced watcher but logs old values instead of the latest. What causes this behavior?

Vue

<script setup>
import { ref, watch } from 'vue'
import { debounce } from 'lodash-es'

const input = ref('')

watch(input, (newVal) => {
  debounce(() => {
    console.log(newVal)
  }, 300)()
})
</script>

A Debounce delays the watcher callback, so it logs the value before changes.

B The debounced function captures the input value only once when created, not on each call.

C The watcher is not triggered because input is not reactive.

D The debounce delay is too short to capture the latest value.

💡 Hint

Check when the debounced function reads the reactive value.

The debounced function closes over newVal at creation time, so it logs the value from when it was created. To fix, pass the value as an argument to the debounced function.

❓ state_output

advanced

What is the console output sequence when rapidly updating a debounced watcher?

Given this Vue 3 code, what will be printed to the console if 'text' changes from '' to 'a', then 'ab', then 'abc' within 100ms intervals?

Vue

<script setup>
import { ref, watch } from 'vue'
import { debounce } from 'lodash-es'

const text = ref('')

const debouncedPrint = debounce((val) => {
  console.log('Value:', val)
}, 200)

watch(text, (val) => {
  debouncedPrint(val)
})

// Simulate rapid changes:
text.value = 'a'
setTimeout(() => { text.value = 'ab' }, 100)
setTimeout(() => { text.value = 'abc' }, 200)
</script>

A No output because debounce blocks all calls

B

Value: a
Value: ab
Value: abc

C Value: a

D Value: abc

💡 Hint

Debounce resets the timer on each call within the delay.

Each change resets the debounce timer. Only the last value 'abc' is logged after 200ms from the last change.

🧠 Conceptual

expert

Why prefer debounced watchers over immediate watchers for expensive operations?

In Vue 3, why is using a debounced watcher better than an immediate watcher for operations like API calls triggered by user input?

A Immediate watchers delay the operation, causing slower UI updates.

B Debounced watchers run the operation immediately on every change, improving responsiveness.

C Debounced watchers reduce the number of times the expensive operation runs by waiting for input to settle.

D Immediate watchers always run only once, so they are less efficient.

💡 Hint

Think about how debounce groups rapid changes into one action.

Debounced watchers wait for a pause in changes before running the operation, preventing excessive calls and improving performance.

Practice

1. What is the main purpose of using a debounced watcher in Vue?

easy

A. To watch multiple data sources at once without delay

B. To delay the reaction to a data change until the changes stop for a short time

C. To prevent any reaction to data changes

D. To immediately react to every single change without delay

Solution

1. Step 1: Understand what debounce means

   Debounce means waiting until changes stop before reacting, avoiding too many reactions.

2. Step 2: Apply debounce to Vue watchers

   Debounced watchers delay the reaction to data changes until the user stops changing the data for a set time.

3. Final Answer:

   To delay the reaction to a data change until the changes stop for a short time -> Option B

4. Quick Check:

   Debounced watcher delays reaction = D [OK]

Hint: Debounced watchers wait before reacting to changes [OK]

Common Mistakes:

• Thinking watchers react immediately without delay
• Confusing debounce with throttling
• Believing debounce stops all reactions

2. Which of the following is the correct way to import a debounce function for use in a Vue watcher?

easy

A. import { watchDebounce } from 'vue-router';

B. import debounce from 'vue';

C. import { debounce } from 'lodash-es';

D. import debounce from 'vue-debounce';

Solution

1. Step 1: Identify common debounce sources

   Lodash-es is a popular library providing debounce functions for JavaScript.

2. Step 2: Check Vue imports

   Vue itself does not export debounce; it must be imported from utility libraries like lodash-es.

3. Final Answer:

   import { debounce } from 'lodash-es'; -> Option C

4. Quick Check:

   Debounce from lodash-es = A [OK]

Hint: Debounce usually comes from lodash or similar libs, not Vue core [OK]

Common Mistakes:

• Trying to import debounce directly from Vue
• Confusing debounce with Vue Router features
• Using incorrect package names

3. Given this Vue 3 setup code, what will be logged when the user types quickly in the input?

import { ref, watch } from 'vue';
import { debounce } from 'lodash-es';

const search = ref('');

watch(search, debounce((newVal) => {
  console.log('Search:', newVal);
}, 300));

medium

A. Logs only once after the user stops typing for 300ms

B. Logs every keystroke immediately

C. Logs nothing because debounce is not working

D. Logs the initial empty string only

Solution

1. Step 1: Understand debounce effect on watcher

   The debounce delays the watcher callback until 300ms after the last change.

2. Step 2: Predict console output

   When typing quickly, the callback waits and logs only once after typing stops for 300ms.

3. Final Answer:

   Logs only once after the user stops typing for 300ms -> Option A

4. Quick Check:

   Debounced watcher logs once after delay = A [OK]

Hint: Debounce batches rapid changes into one delayed call [OK]

Common Mistakes:

• Expecting logs on every keystroke
• Thinking debounce disables logging
• Confusing debounce delay with immediate calls

4. What is wrong with this Vue 3 watcher code using debounce?

import { ref, watch } from 'vue';
import { debounce } from 'lodash-es';

const query = ref('');

watch(query, () => {
  debounce(() => {
    console.log('Query:', query.value);
  }, 500)();
});

medium

A. Debounce is not imported correctly

B. query should be a reactive object, not ref

C. Watcher is missing the immediate option

D. Debounce is called inside watcher callback, creating a new debounced function every time

Solution

1. Step 1: Analyze debounce usage inside watcher

   Debounce is created inside the watcher callback, so a new debounced function is made on every change.

2. Step 2: Understand debounce effect

   This prevents debounce from working properly because the delay resets each time, causing no real debounce.

3. Final Answer:

   Debounce is called inside watcher callback, creating a new debounced function every time -> Option D

4. Quick Check:

   Debounce recreated each call = B [OK]

Hint: Create debounce once outside watcher, not inside callback [OK]

Common Mistakes:

• Defining debounce inside watcher callback
• Forgetting to reuse the same debounced function
• Misunderstanding debounce lifecycle

5. You want to watch a search input and fetch results only after the user stops typing for 400ms. Which is the best way to implement this in Vue 3?

import { ref, watch } from 'vue';
import { debounce } from 'lodash-es';

const searchTerm = ref('');

// What is the correct watcher setup?

hard

A. const debouncedFetch = debounce((val) => fetchResults(val), 400);
watch(searchTerm, (val) => debouncedFetch(val));

B. watch(searchTerm, () => debounce((val) => fetchResults(val), 400));

C. watch(searchTerm, (val) => fetchResults(val)); // no debounce

D. const debouncedFetch = debounce(fetchResults, 400);
watch(searchTerm, debouncedFetch());

Solution

1. Step 1: Create debounce function once

   Define debouncedFetch outside watcher to keep the same debounced function.

2. Step 2: Use watcher to call debounced function

   Watcher calls debouncedFetch with new value, so fetchResults runs after 400ms of no changes.

3. Final Answer:

   const debouncedFetch = debounce((val) => fetchResults(val), 400); watch(searchTerm, (val) => debouncedFetch(val)); -> Option A

4. Quick Check:

   Debounce created once, watcher calls it = C [OK]

Hint: Define debounce once, call it inside watcher callback [OK]

Common Mistakes:

• Calling debounce inside watcher callback directly
• Not passing the value to debounced function
• Calling debounced function immediately instead of passing reference