Why JavaScript hooks for transitions in Vue? - Purpose & Use Cases

The Big Idea

Discover how to make your app's animations feel effortless and flawless with just a few hooks!

The Scenario

Imagine you want to animate a box fading in and sliding down when it appears on the page, and then fading out and sliding up when it disappears.

You try to do this by manually adding and removing CSS classes and timers in your code.

The Problem

Manually controlling animations with timers and class changes is tricky and easy to get wrong.

You might forget to remove classes, causing animations to freeze or jump.

It's hard to keep track of when animations start and end, making your code messy and buggy.

The Solution

JavaScript hooks for transitions let you run code exactly when an element starts or finishes entering or leaving.

This means you can smoothly control animations and clean up after them without messy timers or guesswork.

Before vs After

✗ Before

element.classList.add('fade-in'); setTimeout(() => element.classList.remove('fade-in'), 500);

✓ After

<transition @before-enter="startFadeIn" @after-leave="cleanup">...</transition>

What It Enables

You can create smooth, reliable animations that react perfectly to your app's state changes.

Real Life Example

When a notification pops up, it gracefully fades and slides in, then disappears with a smooth exit animation, all handled cleanly with hooks.

Key Takeaways

Manual animation control is error-prone and hard to maintain.

JavaScript hooks run code at exact animation moments for smooth transitions.

This makes your UI feel polished and your code easier to manage.

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