JavaScript hooks for transitions in Vue - Performance & Optimization

Performance: JavaScript hooks for transitions

MEDIUM IMPACT

This affects the smoothness and timing of animations during component state changes, impacting interaction responsiveness and visual stability.

Animating component entry and exit with JavaScript hooks

Vue

const hooks = {
  beforeEnter(el) {
    el.style.opacity = '0';
  },
  enter(el, done) {
    requestAnimationFrame(() => {
      el.style.transition = 'opacity 0.5s';
      el.style.opacity = '1';
      setTimeout(done, 500);
    });
  }
};

Defers style changes to the next frame, avoiding blocking the main thread and ensuring smooth animation.

📈 Performance GainNon-blocking animation, reduces input delay and improves frame rate

Animating component entry and exit with JavaScript hooks

Vue

const hooks = {
  beforeEnter(el) {
    // heavy synchronous logic
    for(let i = 0; i < 100000000; i++) {}
    el.style.opacity = '0';
  },
  enter(el, done) {
    el.style.transition = 'opacity 0.5s';
    el.style.opacity = '1';
    setTimeout(done, 500);
  }
};

Heavy synchronous code blocks the main thread, causing janky animations and delayed user interaction.

📉 Performance CostBlocks rendering for 100+ ms, causing input delay and animation jank

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy synchronous logic in hooks	Multiple style changes	Multiple reflows triggered	High paint cost due to layout thrashing	[X] Bad
Lightweight hooks with requestAnimationFrame	Minimal style changes	Single reflow	Low paint cost with smooth animation	[OK] Good

Rendering Pipeline

JavaScript hooks run during transition phases and can trigger style recalculations and layout changes. Heavy synchronous work delays Style Calculation and Layout, causing frame drops.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution blocking Style Calculation and Layout

Core Web Vital Affected

INP

This affects the smoothness and timing of animations during component state changes, impacting interaction responsiveness and visual stability.

Optimization Tips

1Avoid heavy synchronous logic inside transition hooks to prevent blocking the main thread.

2Use requestAnimationFrame to schedule style changes for smoother animations.

3Minimize DOM and style changes during transitions to reduce reflows and paints.

Performance Quiz - 3 Questions

What is the main performance risk of running heavy synchronous code inside Vue transition JavaScript hooks?

A It blocks the main thread causing animation jank and input delay.

B It increases the bundle size significantly.

C It causes the browser to skip the animation entirely.

D It improves animation smoothness by precomputing styles.

DevTools: Performance

How to check: Record a performance profile while triggering the transition. Look for long tasks in the Main thread during the animation phase.

What to look for: Long blocking JavaScript tasks causing frame drops and delayed style recalculations indicate poor performance.

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