onUpdated and onBeforeUpdate in Vue - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Understanding onBeforeUpdate timing

In a Vue 3 component using the Composition API, when does the onBeforeUpdate lifecycle hook run?

Choose the correct description of its timing relative to the DOM update.

A It runs right before the component's reactive data changes.

B It runs after the DOM has been updated with the new data.

C It runs only once when the component is first created.

D It runs right before the DOM updates but after reactive data changes.

💡 Hint

Think about when Vue needs to prepare the DOM before showing changes.

The onBeforeUpdate hook runs after reactive data changes but before the DOM updates. This lets you perform actions or checks before the DOM reflects the new state.

❓ component_behavior

intermediate

Effect of onUpdated hook on DOM

What happens when the onUpdated lifecycle hook runs in a Vue 3 component?

Choose the correct statement about its effect on the DOM.

A It runs after the DOM has updated and can access the new DOM state.

B It runs before the DOM updates and can cancel the update.

C It runs only if the component's props change, not reactive data.

D It runs before the component is mounted.

💡 Hint

Consider when you want to read or manipulate the updated DOM.

The onUpdated hook runs after the DOM updates, so you can safely access or manipulate the new DOM state.

❓ state_output

advanced

Output order of onBeforeUpdate and onUpdated

Given this Vue 3 component code, what is the order of console logs when the button is clicked?

import { ref, onBeforeUpdate, onUpdated } from 'vue';

export default {
  setup() {
    const count = ref(0);
    onBeforeUpdate(() => console.log('Before Update'));
    onUpdated(() => console.log('Updated'));
    function increment() {
      count.value++;
    }
    return { count, increment };
  }
}

When the button triggers increment(), what logs appear and in what order?

A Updated, Before Update

B Before Update, Updated

C Before Update only

D Updated only

💡 Hint

Remember the lifecycle hooks run around the DOM update.

When reactive data changes, onBeforeUpdate runs first before the DOM updates, then onUpdated runs after the DOM updates.

🔧 Debug

advanced

Why does onUpdated not run?

A developer writes this Vue 3 component:

import { ref, onUpdated } from 'vue';

export default {
  setup() {
    const message = ref('Hello');
    onUpdated(() => console.log('Component updated'));
    function changeMessage() {
      message.value = 'Hi';
    }
    return { message, changeMessage };
  }
}

But when changeMessage() is called, the console log never appears. What is the most likely reason?

A The component is not mounted, so lifecycle hooks don't run.

B The <code>onUpdated</code> hook only runs on prop changes, not reactive refs.

C The component's template does not use <code>message</code>, so no DOM update occurs.

D The <code>message</code> ref is not reactive, so no update triggers.

💡 Hint

Think about when Vue triggers DOM updates.

If the reactive data changes but is not used in the template, Vue does not update the DOM, so onUpdated does not run.

🧠 Conceptual

expert

Distinguishing onBeforeUpdate and onUpdated use cases

Which scenario best fits using onBeforeUpdate instead of onUpdated in a Vue 3 component?

A You want to save the current DOM state before it changes for comparison.

B You want to fetch new data after the component updates.

C You want to measure the DOM size after it changes to adjust layout.

D You want to initialize data when the component mounts.

💡 Hint

Think about when you need to capture the old state before changes.

onBeforeUpdate runs before the DOM changes, so it's ideal to capture the current DOM state before updates. onUpdated runs after the DOM changes.