onUpdated and onBeforeUpdate in Vue - Mini Project: Build & Apply

Using onUpdated and onBeforeUpdate in Vue 3

📖 Scenario: You are building a simple Vue 3 app that shows a counter. You want to see messages in the console right before the component updates and right after it updates. This helps you understand when Vue updates the screen.

🎯 Goal: Create a Vue 3 component that uses onBeforeUpdate and onUpdated lifecycle hooks to log messages to the console when the counter changes.

📋 What You'll Learn

Create a reactive counter variable starting at 0

Add a button to increase the counter by 1 when clicked

Use onBeforeUpdate to log 'Before update: counter is X' where X is the counter value

Use onUpdated to log 'Updated: counter is X' where X is the counter value

💡 Why This Matters

🌍 Real World

Developers often need to know when a component updates to perform side effects like animations, analytics, or syncing data.

💼 Career

Understanding Vue lifecycle hooks is essential for building interactive and efficient Vue applications in professional frontend development.

1

Set up the reactive counter

Create a Vue 3 component with a reactive variable called counter initialized to 0 using ref.

Vue

import { ref } from 'vue'

// Create a reactive variable called counter and set it to 0
// Your code here



  
    Counter: {{ counter }}
  

Hint

Use ref(0) to create a reactive counter variable.

2

Add a button to increase the counter

Add a button inside the <template> that increases counter.value by 1 when clicked. Use @click event with an inline arrow function.

Vue

import { ref } from 'vue'

const counter = ref(0)



  
    Counter: {{ counter }}
    
    
  

Hint

Use @click="counter.value++" on the button to increase the counter.

3

Use onBeforeUpdate to log before update

Import onBeforeUpdate from 'vue' and use it to log 'Before update: counter is ' + counter.value before the component updates.

Vue

import { ref, onBeforeUpdate } from 'vue'

const counter = ref(0)

// Use onBeforeUpdate to log before update
// Your code here



  
    Counter: {{ counter }}
    Increase
  

Hint

Use onBeforeUpdate(() => { ... }) to run code before the update.

4

Use onUpdated to log after update

Import onUpdated from 'vue' and use it to log 'Updated: counter is ' + counter.value after the component updates.

Vue

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

const counter = ref(0)

onBeforeUpdate(() => {
  console.log('Before update: counter is ' + counter.value)
})

// Use onUpdated to log after update
// Your code here



  
    Counter: {{ counter }}
    Increase
  

Hint

Use onUpdated(() => { ... }) to run code after the update.

Practice

1. What is the main difference between onBeforeUpdate and onUpdated in Vue?

easy

A. onUpdated runs only once when the component mounts.

B. onBeforeUpdate runs after the screen updates; onUpdated runs before.

C. Both run at the same time during the update.

D. onBeforeUpdate runs before the screen updates; onUpdated runs after.

Solution

1. Step 1: Understand lifecycle timing

   onBeforeUpdate triggers just before Vue updates the DOM to reflect data changes.

2. Step 2: Identify post-update hook

   onUpdated triggers right after the DOM has been updated.

3. Final Answer:

   onBeforeUpdate runs before the screen updates; onUpdated runs after. -> Option D

4. Quick Check:

   Before update = onBeforeUpdate, After update = onUpdated [OK]

Hint: Remember: before update = before screen changes, after update = after screen changes [OK]

Common Mistakes:

• Confusing the order of hooks
• Thinking both run at the same time
• Assuming onUpdated runs only once

2. Which of the following is the correct way to import and use onBeforeUpdate in a Vue 3 component?

easy

A. import { onBeforeUpdate } from 'vue'; onBeforeUpdate(() => { console.log('Before update'); });

B. import onBeforeUpdate from 'vue'; onBeforeUpdate(() => { console.log('Before update'); });

C. import { onBeforeUpdate } from 'vue'; onBeforeUpdate = () => { console.log('Before update'); };

D. import { onBeforeUpdate } from 'vue'; onBeforeUpdate.log('Before update');

Solution

1. Step 1: Check import syntax

   Vue exports onBeforeUpdate as a named export, so use curly braces in import.

2. Step 2: Use hook as a function

   Call onBeforeUpdate with a callback function to run code before update.

3. Final Answer:

   import { onBeforeUpdate } from 'vue'; onBeforeUpdate(() => { console.log('Before update'); }); -> Option A

4. Quick Check:

   Named import + callback function = import { onBeforeUpdate } from 'vue'; onBeforeUpdate(() => { console.log('Before update'); }); [OK]

Hint: Use curly braces for named imports and pass a function [OK]

Common Mistakes:

• Importing without curly braces
• Assigning hook to a variable instead of calling it
• Trying to call a method on the hook

3. Given this Vue 3 setup code, what will be logged to the console when count changes from 0 to 1?

import { ref, onBeforeUpdate, onUpdated } from 'vue';
export default {
  setup() {
    const count = ref(0);
    onBeforeUpdate(() => console.log('Before update:', count.value));
    onUpdated(() => console.log('After update:', count.value));
    return { count };
  }
}

medium

A. After update: 1
Before update: 0

B. Before update: 1
After update: 1

C. Before update: 0
After update: 1

D. Before update: 1
After update: 0

Solution

1. Step 1: Understand timing of hooks

   onBeforeUpdate runs after reactive data updated (to 1) but before DOM updates, so count.value is 1.

2. Step 2: Check onUpdated timing

   onUpdated runs after DOM updates, count.value is 1.

3. Final Answer:

   Before update: 1 After update: 1 -> Option B

4. Quick Check:

   Both hooks log new value [OK]

Hint: Both hooks log new value; they time relative to DOM update [OK]

Common Mistakes:

• Thinking onBeforeUpdate logs old value
• Mixing order of logs
• Thinking onBeforeUpdate runs after value changes

4. What is wrong with this Vue 3 code snippet using onBeforeUpdate and onUpdated?

import { ref, onBeforeUpdate, onUpdated } from 'vue';
export default {
  setup() {
    const count = ref(0);
    onBeforeUpdate = () => console.log('Before update');
    onUpdated(() => console.log('After update'));
    count.value++;
    return { count };
  }
}

medium

A. Assigning a function to onBeforeUpdate instead of calling it.

B. Missing import of onBeforeUpdate.

C. Using count.value++ instead of count++.

D. Not returning count from setup.

Solution

1. Step 1: Check hook usage

   The code assigns a function to onBeforeUpdate instead of calling it with a callback.

2. Step 2: Confirm other parts

   Imports are correct, count.value++ is valid, and count is returned properly.

3. Final Answer:

   Assigning a function to onBeforeUpdate instead of calling it. -> Option A

4. Quick Check:

   Hooks must be called, not reassigned [OK]

Hint: Call hooks with functions, don't assign them [OK]

Common Mistakes:

• Assigning hooks instead of calling
• Forgetting to import hooks
• Misusing ref value increment

5. You want to log the previous and current value of a reactive variable score every time it updates in a Vue 3 component. Which approach correctly uses onBeforeUpdate and onUpdated to achieve this?

import { ref, onBeforeUpdate, onUpdated } from 'vue';
export default {
  setup() {
    const score = ref(0);
    let oldScore = 0;

    onBeforeUpdate(() => {
      oldScore = score.value;
    });

    onUpdated(() => {
      console.log(`Score changed from ${oldScore} to ${score.value}`);
    });

    return { score };
  }
}

hard

A. This code correctly logs the previous and current score values on update.

B. This code will cause an infinite loop because score.value changes inside hooks.

C. This code logs the same value twice because oldScore is set to the new value in onBeforeUpdate.

D. This code misses importing onUpdated, so it will fail.

Solution

1. Step 1: Understand hook order

   onBeforeUpdate runs after data updated, so sets oldScore to new value.

2. Step 2: Confirm logging after update

   onUpdated logs new value for both old and current.

3. Final Answer:

   This code logs the same value twice because oldScore is set to the new value in onBeforeUpdate. -> Option C

4. Quick Check:

   onBeforeUpdate cannot capture old ref value; use watch() instead [OK]

Hint: Data updates before onBeforeUpdate; capture old values with watch(newVal, oldVal) [OK]

Common Mistakes:

• Thinking onBeforeUpdate sees old data value
• Expecting old/new to differ with this pattern
• Fearing infinite loops from hook logic