onUpdated and onBeforeUpdate in Vue - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the lifecycle hook that runs before the component updates.

Vue

import { [1] } from 'vue';

Drag options to blanks, or click blank then click option'

AonMounted

BonBeforeUpdate

ConUpdated

DonCreated

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing onMounted because it runs only once after mounting.

Choosing onUpdated which runs after the update, not before.

The onBeforeUpdate hook runs just before the component updates its DOM.

2fill in blank

medium

Complete the code to import the lifecycle hook that runs after the component updates.

Vue

import { [1] } from 'vue';

Drag options to blanks, or click blank then click option'

AonUpdated

BonUnmounted

ConBeforeUpdate

DonMounted

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing onBeforeUpdate which runs before the update.

Choosing onMounted which runs only once after mounting.

The onUpdated hook runs after the component's DOM has updated.

3fill in blank

hard

Fix the error in the code by choosing the correct lifecycle hook to run code before the DOM updates.

Vue

export default {
  setup() {
    [1](() => {
      console.log('DOM will update soon');
    });
  }
}

Drag options to blanks, or click blank then click option'

AonUpdated

BonMounted

ConUnmounted

DonBeforeUpdate

Attempts:

3 left

💡 Hint

Common Mistakes

Using onUpdated which runs after the DOM updates.

Using onMounted which runs only once after mounting.

onBeforeUpdate runs before the DOM updates, so it is the correct hook here.

4fill in blank

hard

Fill both blanks to correctly use the hooks that run before and after the component updates.

Vue

import { [1], [2] } from 'vue';

export default {
  setup() {
    [1](() => {
      console.log('Before update');
    });
    [2](() => {
      console.log('After update');
    });
  }
}

Drag options to blanks, or click blank then click option'

AonBeforeUpdate

BonMounted

ConUpdated

DonUnmounted

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the hooks' order.

Using onMounted or onUnmounted instead.

onBeforeUpdate runs before the update, and onUpdated runs after the update.

5fill in blank

hard

Fill all three blanks to create a Vue component that logs messages before update, after update, and when mounted.

Vue

import { [1], [2], [3] } from 'vue';

export default {
  setup() {
    [1](() => {
      console.log('Component mounted');
    });
    [2](() => {
      console.log('Before update');
    });
    [3](() => {
      console.log('After update');
    });
  }
}

Drag options to blanks, or click blank then click option'

AonMounted

BonBeforeUpdate

ConUpdated

DonUnmounted

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the order of hooks.

Using onUnmounted instead of onMounted.

onMounted runs once when the component mounts, onBeforeUpdate runs before each update, and onUpdated runs after each 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