JavaScript hooks for transitions in Vue - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are JavaScript hooks in Vue transitions?

JavaScript hooks are special functions you can add to Vue's transition component to run code at specific moments during an element's entering or leaving animation, like before it starts or after it ends.

beginner

Name the four main JavaScript hooks used in Vue transitions.

The four main hooks are: <strong>before-enter</strong>, <strong>enter</strong>, <strong>leave</strong>, and <strong>after-leave</strong>. They let you control what happens before and during entering and leaving animations.

intermediate

How does the enter hook work in Vue transitions?

The enter hook runs when an element starts to appear. You can use it to add classes or styles to animate the element. It also receives a callback to tell Vue when the animation is done.

intermediate

Why use JavaScript hooks instead of CSS-only transitions in Vue?

JavaScript hooks let you run custom code during transitions, like starting complex animations, controlling timing precisely, or triggering other actions. CSS-only transitions are simpler but less flexible.

intermediate

What is the role of the callback function in Vue's enter and leave hooks?

The callback tells Vue when your JavaScript animation or transition is finished. Vue waits for this callback before removing or showing the element, ensuring smooth animations.

Which Vue transition hook runs right before an element starts to enter?

A leave

B enter

C before-enter

D after-leave

The before-enter hook runs just before the element begins its entering animation.

In Vue transitions, what must you call inside the enter hook to signal animation completion?

A done() callback

B start() function

C finish() method

D end() event

You call the done() callback to tell Vue the enter animation is finished.

Which hook would you use to run code after an element has fully left the DOM?

A after-leave

B enter

C leave

D before-enter

The after-leave hook runs after the element has been removed from the DOM.

Why might you choose JavaScript hooks over CSS transitions in Vue?

A Because JavaScript hooks are easier to write

B Because CSS transitions are slower

C To avoid using classes

D To run custom code during animations

JavaScript hooks let you run custom code during transitions, offering more control.

Which Vue transition hook is called when an element starts to leave?

A enter

B leave

C before-enter

D after-leave

The leave hook runs when an element begins its leaving animation.

Explain how JavaScript hooks control the timing of transitions in Vue.

Think about how Vue waits for your code to finish before changing the element.

Describe a simple example of using the enter and leave hooks in a Vue transition.

Imagine fading an element in and out with JavaScript hooks.

Practice

1. What is the main purpose of JavaScript hooks in Vue transitions?

easy

A. To run custom code at specific moments during enter and leave transitions

B. To replace CSS animations completely

C. To define the HTML structure of a component

D. To manage Vue component state

Solution

1. Step 1: Understand what JavaScript hooks do in Vue transitions

   JavaScript hooks allow you to run code at key moments during the enter and leave phases of a transition.

2. Step 2: Compare options with this understanding

   Only To run custom code at specific moments during enter and leave transitions correctly describes this purpose. Options B, C, and D describe unrelated concepts.

3. Final Answer:

   To run custom code at specific moments during enter and leave transitions -> Option A

4. Quick Check:

   JavaScript hooks = run code during transitions [OK]

Hint: Hooks run code during enter/leave, not replace CSS [OK]

Common Mistakes:

• Thinking hooks replace CSS animations
• Confusing hooks with component state management
• Believing hooks define HTML structure

2. Which of the following is the correct syntax to define a JavaScript hook for the beforeEnter phase in a Vue transition component?

easy

A. <transition v-on:before-enter="myHook">

B. <transition v-on:beforeEnter="myHook">

C. <transition @before-enter="myHook">

D. <transition @beforeEnter="myHook">

Solution

1. Step 1: Recall Vue event naming conventions for transitions

   Vue uses kebab-case event names for transition hooks, like before-enter, and the shorthand @ for v-on:.

2. Step 2: Match the correct syntax

   <transition @before-enter="myHook"> uses @before-enter, which is correct. Options A, C, and D use camelCase or incorrect casing.

3. Final Answer:

   <transition @before-enter="myHook"> -> Option C

4. Quick Check:

   Vue transition hooks use kebab-case with @ [OK]

Hint: Use kebab-case and @ for Vue transition hooks [OK]

Common Mistakes:

• Using camelCase event names
• Mixing v-on: and @ incorrectly
• Capitalizing event names

3. Given this Vue transition component snippet, what will be logged when the element starts entering?

<transition @enter="onEnter">
  <div v-if="show">Hello</div>
</transition>

medium

A. Nothing is logged because show is initially false

B. Throws an error because done() is called synchronously

C. Logs 'Enter started' immediately on page load

D. Logs 'Enter started' after 1 second when element appears

Solution

1. Step 1: Understand the timing of the show variable

   Initially, show is false, so the element is not rendered. After 1 second, show becomes true, triggering the enter transition.

2. Step 2: Analyze the enter hook behavior

   The onEnter hook logs 'Enter started' and calls done() immediately. This happens after 1 second when the element appears.

3. Final Answer:

   Logs 'Enter started' after 1 second when element appears -> Option D

4. Quick Check:

   Enter hook logs on element show [OK]

Hint: Enter hook runs when element appears, not on load [OK]

Common Mistakes:

• Thinking enter hook runs immediately on load
• Assuming no log because initial show is false
• Believing done() call causes error

4. Identify the error in this Vue transition JavaScript hook code:

<transition @leave="onLeave">
  <div v-if="visible">Bye</div>
</transition>

medium

A. Calling done() immediately before animation finishes causes transition to end too soon

B. Missing a return statement in onLeave function

C. Using setTimeout inside onLeave is not allowed

D. v-if should be v-show for transitions

Solution

1. Step 1: Understand the leave hook timing

   The onLeave hook should call done() only after the animation finishes to keep the element during transition.

2. Step 2: Analyze the code's done() call

   Here, done() is called immediately, but the opacity change happens after 500ms, so the transition ends too soon.

3. Final Answer:

   Calling done() immediately before animation finishes causes transition to end too soon -> Option A

4. Quick Check:

   done() must wait for animation end [OK]

Hint: Call done() only after animation completes [OK]

Common Mistakes:

• Calling done() too early
• Confusing v-if and v-show for transitions
• Thinking setTimeout is disallowed in hooks

5. You want to create a fade transition that delays the leave animation until a custom API call finishes. Which approach correctly uses JavaScript hooks to achieve this?

<transition @leave="handleLeave">
  <div v-if="show">Content</div>
</transition>

<script setup>
const show = ref(true)
async function apiCall() {
  return new Promise(resolve => setTimeout(resolve, 1000))
}

function handleLeave(el, done) {
  // What should go here?
}
</script>

hard

A. Set opacity to 0, call done(), then call apiCall()

B. Call apiCall(), then in .then() set opacity to 0 and call done()

C. Call done() immediately, then call apiCall()

D. Do nothing in handleLeave; rely on CSS only

Solution

1. Step 1: Understand the goal

   The leave transition should wait for the API call to finish before starting the fade out and completing the transition.

2. Step 2: Use async logic in the leave hook

   Call apiCall(), then after it resolves, set opacity to 0 and call done() to signal transition end.

3. Final Answer:

   Call apiCall(), then in .then() set opacity to 0 and call done() -> Option B

4. Quick Check:

   Wait async, then animate and done() [OK]

Hint: Wait async call before done() in leave hook [OK]

Common Mistakes:

• Calling done() before async finishes
• Ignoring async and relying on CSS only
• Calling done() too early, skipping animation