onBeforeMount and onBeforeUnmount in Vue - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the onBeforeMount lifecycle hook in Vue?

onBeforeMount runs just before the component is added to the page. It lets you run code right before the component appears on screen.

beginner

When does onBeforeUnmount run in a Vue component?

onBeforeUnmount runs right before the component is removed from the page. It is useful to clean up things like timers or event listeners.

intermediate

How do onBeforeMount and onBeforeUnmount help manage resources in Vue components?

<p>They let you start or stop tasks at the right time. For example, start a timer before showing the component and stop it before removing the component to avoid memory leaks.</p>

beginner

Show a simple example of using onBeforeMount and onBeforeUnmount in Vue's <script setup>.

<pre>import { onBeforeMount, onBeforeUnmount } from 'vue'

onBeforeMount(() =&gt; {
  console.log('Component will mount soon')
})

onBeforeUnmount(() =&gt; {
  console.log('Component will unmount soon')
})</pre>

intermediate

Why is it important to use onBeforeUnmount to clean up in Vue components?

Cleaning up prevents problems like memory leaks or unwanted background tasks running after the component is gone. It keeps your app fast and stable.

When does onBeforeMount run in a Vue component?

A Right after the component is removed from the DOM

B Right before the component is added to the DOM

C After the component is mounted

D When the component is updated

onBeforeMount runs just before the component is added to the page (DOM).

What is a common use for onBeforeUnmount in Vue?

A To update the component's state

B To start a timer when the component loads

C To fetch data from an API

D To clean up event listeners before the component is removed

onBeforeUnmount is used to clean up things like event listeners before the component is removed.

Which Vue lifecycle hook runs after the component is mounted?

A onMounted

B onBeforeMount

C onBeforeUnmount

D onUpdated

onMounted runs after the component is added to the DOM.

What happens if you forget to clean up in onBeforeUnmount?

A Memory leaks or unwanted background tasks may occur

B The component will never unmount

C The component will mount twice

D Nothing, cleanup is optional

Not cleaning up can cause memory leaks or background tasks to keep running, slowing down your app.

Which of these is true about onBeforeMount and onBeforeUnmount?

A Both run after the component is mounted

B Both run before the component is added to the DOM

C <code>onBeforeMount</code> runs before mounting, <code>onBeforeUnmount</code> runs before unmounting

D They run only when the component updates

onBeforeMount runs before mounting, and onBeforeUnmount runs before unmounting the component.

Explain in your own words what onBeforeMount and onBeforeUnmount do in a Vue component.

Think about what happens right before a component shows or hides.

Describe a real-life example where you might use onBeforeUnmount in a Vue app.

Imagine turning off things when leaving a room.

Practice

1. What is the main purpose of the onBeforeMount lifecycle hook in Vue?

easy

A. It runs when the component is updated.

B. It runs after the component is removed from the screen.

C. It runs only once when the app starts.

D. It runs right before the component appears on the screen.

Solution

1. Step 1: Understand the timing of onBeforeMount

   The onBeforeMount hook runs just before the component is rendered and shown on the screen.

2. Step 2: Compare with other lifecycle hooks

   Unlike hooks that run after removal or updates, onBeforeMount is specifically before the first render.

3. Final Answer:

   It runs right before the component appears on the screen. -> Option D

4. Quick Check:

   onBeforeMount = before component appears [OK]

Hint: onBeforeMount = just before showing component [OK]

Common Mistakes:

• Confusing onBeforeMount with onBeforeUnmount
• Thinking it runs after component removal
• Mixing it with update hooks

2. Which of the following is the correct way to use onBeforeUnmount inside the setup() function in Vue 3?

easy

A. onBeforeUnmount(function) { console.log('Unmount') }

B. onBeforeUnmount = () => { console.log('Component will unmount') }

C. onBeforeUnmount(() => { console.log('Component will unmount') })

D. setup(() => { onBeforeUnmount(console.log('Unmount')) })

Solution

1. Step 1: Recall correct syntax for lifecycle hooks in setup()

   Lifecycle hooks like onBeforeUnmount are called as functions with a callback inside setup().

2. Step 2: Identify correct arrow function usage

   onBeforeUnmount(() => { console.log('Component will unmount') }) correctly passes an arrow function to onBeforeUnmount to run code before unmount.

3. Final Answer:

   onBeforeUnmount(() => { console.log('Component will unmount') }) -> Option C

4. Quick Check:

   Use onBeforeUnmount(callback) inside setup() [OK]

Hint: Use onBeforeUnmount(() => {...}) inside setup() [OK]

Common Mistakes:

• Assigning onBeforeUnmount instead of calling it
• Calling onBeforeUnmount with wrong syntax
• Trying to use it outside setup()

3. Consider this Vue 3 component code snippet inside setup():

import { ref, onBeforeMount, onBeforeUnmount } from 'vue'

export default {
  setup() {
    const count = ref(0)
    onBeforeMount(() => { count.value = 5 })
    onBeforeUnmount(() => { count.value = 0 })
    return { count }
  }
}

What will be the value of count just before the component is removed from the screen?

medium

A. 0

B. 5

C. undefined

D. It causes an error

Solution

1. Step 1: Understand onBeforeMount effect

   When the component is about to mount, count.value is set to 5.

2. Step 2: Understand onBeforeUnmount effect

   Right before the component unmounts, count.value is reset to 0.

3. Final Answer:

   0 -> Option A

4. Quick Check:

   onBeforeUnmount resets count to 0 [OK]

Hint: onBeforeUnmount runs last, resetting count to 0 [OK]

Common Mistakes:

• Thinking count stays 5 after unmount
• Confusing onBeforeMount and onBeforeUnmount effects
• Assuming unmount hook does not change reactive data

4. What is wrong with this Vue 3 code inside setup()?

import { onBeforeUnmount } from 'vue'

export default {
  setup() {
    onBeforeUnmount = () => {
      console.log('Cleaning up')
    }
  }
}

medium

A. Missing import of onBeforeMount.

B. onBeforeUnmount is assigned instead of called with a callback.

C. Arrow function syntax is incorrect.

D. setup() must return a value.

Solution

1. Step 1: Check how onBeforeUnmount is used

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

2. Step 2: Correct usage of onBeforeUnmount

   It should be called like onBeforeUnmount(() => { ... }) to register the cleanup function.

3. Final Answer:

   onBeforeUnmount is assigned instead of called with a callback. -> Option B

4. Quick Check:

   Use onBeforeUnmount(callback), not assignment [OK]

Hint: Call onBeforeUnmount(callback), don't assign it [OK]

Common Mistakes:

• Assigning lifecycle hook instead of calling it
• Forgetting parentheses for function call
• Confusing import errors with usage errors

5. You want to track how many times a component is about to mount and unmount using onBeforeMount and onBeforeUnmount. Which code correctly updates two counters mountCount and unmountCount inside setup()?

hard

A. const mountCount = ref(0); const unmountCount = ref(0);
onBeforeMount(() => { mountCount.value++ });
onBeforeUnmount(() => { unmountCount.value++ });
return { mountCount, unmountCount }

B. let mountCount = 0; let unmountCount = 0;
onBeforeMount(() => { mountCount++ });
onBeforeUnmount(() => { unmountCount++ });
return { mountCount, unmountCount }

C. const mountCount = 0; const unmountCount = 0;
onBeforeMount(() => { mountCount += 1 });
onBeforeUnmount(() => { unmountCount += 1 });
return { mountCount, unmountCount }

D. const mountCount = ref(0); const unmountCount = ref(0);
onBeforeMount(() => mountCount++);
onBeforeUnmount(() => unmountCount++);
return { mountCount, unmountCount }

Solution

1. Step 1: Use reactive refs for counters

   To track changes reactively, counters must be ref(0), not plain numbers.

2. Step 2: Increment ref values inside lifecycle hooks

   Inside onBeforeMount and onBeforeUnmount, increment with mountCount.value++ and unmountCount.value++.

3. Step 3: Return refs for template usage

   Return the refs so the template can react to changes.

4. Final Answer:

   const mountCount = ref(0); const unmountCount = ref(0); onBeforeMount(() => { mountCount.value++ }); onBeforeUnmount(() => { unmountCount.value++ }); return { mountCount, unmountCount } -> Option A

5. Quick Check:

   Use ref(0) and increment .value inside hooks [OK]

Hint: Use ref(0) and increment .value inside hooks [OK]

Common Mistakes:

• Using plain numbers instead of refs
• Incrementing refs without .value
• Not returning counters for template