Why advanced patterns matter in Vue - Performance Evidence

Performance: Why advanced patterns matter

HIGH IMPACT

This concept affects how efficiently Vue apps render and update, impacting page load speed and interaction responsiveness.

Updating a list with many items efficiently

Vue

<template>
  <ul>
    <ListItem v-for="item in items" :key="item.id" :item="item" />
  </ul>
</template>

<script setup>
import { ref, reactive } from 'vue'
import ListItem from './ListItem.vue'
const items = ref([...Array(1000)].map((_, i) => reactive({ id: i, name: `Item ${i}` })))

function updateAll() {
  items.value.forEach(item => { item.name += ' updated' })
}
</script>

Using a child component with props and mutating items in place avoids recreating the whole list, reducing re-renders.

📈 Performance GainOnly updated items re-render, reducing DOM updates and improving interaction responsiveness.

Updating a list with many items efficiently

Vue

<template>
  <ul>
    <li v-for="item in items" :key="item.id">
      {{ item.name }}
    </li>
  </ul>
</template>

<script setup>
import { ref } from 'vue'
const items = ref([...Array(1000)].map((_, i) => ({ id: i, name: `Item ${i}` })))

function updateAll() {
  items.value = items.value.map(item => ({ ...item, name: item.name + ' updated' }))
}
</script>

Recreating all items triggers Vue to re-render every list item, causing many DOM updates and slow interaction.

📉 Performance CostTriggers 1000 re-renders and many DOM updates, causing slow interaction and high CPU usage.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Recreate entire list on update	Many DOM nodes replaced	1000 reflows	High paint cost	[X] Bad
Update items in place with child components	Minimal DOM changes	Few reflows	Low paint cost	[OK] Good

Rendering Pipeline

Vue tracks reactive data changes and schedules component updates. Advanced patterns minimize unnecessary updates, reducing layout recalculations and paints.

→Reactive Dependency Tracking

→Virtual DOM Diffing

→DOM Updates

→Paint

⚠️ BottleneckDOM Updates stage is most expensive due to layout recalculations and repaints.

Core Web Vital Affected

INP

This concept affects how efficiently Vue apps render and update, impacting page load speed and interaction responsiveness.

Optimization Tips

1Avoid recreating large reactive arrays; update items in place when possible.

2Use child components to isolate updates and reduce re-render scope.

3Always provide stable keys in v-for loops to help Vue track elements efficiently.

Performance Quiz - 3 Questions

Why do advanced Vue patterns improve interaction performance?

A They increase the number of reactive variables.

B They reduce unnecessary component re-renders and DOM updates.

C They add more watchers to track changes.

D They force Vue to recreate the entire DOM tree.

DevTools: Performance

How to check: Record a performance profile while triggering updates; look for long scripting and rendering tasks.

What to look for: Look for many small DOM updates and long frames indicating slow re-renders; fewer updates mean better performance.

Practice

1. Why do advanced patterns like the Composition API matter in Vue apps?

easy

A. They remove the need for any JavaScript in Vue components.

B. They make the app run slower but look nicer.

C. They help organize code better and make it reusable across components.

D. They only work with Vue 2 and older versions.

Solution

1. Step 1: Understand the role of advanced patterns

   Advanced patterns like the Composition API help organize code logically and improve reuse.

2. Step 2: Eliminate incorrect options

   The other options wrongly claim advanced patterns remove JavaScript, make apps slower, or limit to Vue 2.

3. Final Answer:

   They help organize code better and make it reusable across components. -> Option C

4. Quick Check:

   Advanced patterns improve code clarity and reuse [OK]

Hint: Advanced patterns improve reuse and clarity in Vue code [OK]

Common Mistakes:

• Thinking advanced patterns slow down the app
• Confusing Vue 2 and Vue 3 features
• Believing advanced patterns remove JavaScript

2. Which of the following is the correct syntax to define a composable function in Vue 3?

easy

A. function useCounter() { const count = ref(0); return { count }; }

B. const useCounter = () => { let count = 0; return count; }

C. function useCounter() { let count = 0; console.log(count); }

D. const useCounter = function() { count = ref(0); }

Solution

1. Step 1: Identify proper composable pattern

   A composable returns reactive state like ref and exposes it for reuse.

2. Step 2: Check each option's correctness

   function useCounter() { const count = ref(0); return { count }; } correctly uses ref and returns count. The others fail by returning plain numbers, only logging, or missing declarations/returns.

3. Final Answer:

   function useCounter() { const count = ref(0); return { count }; } -> Option A

4. Quick Check:

   Composable returns reactive state [OK]

Hint: Composable must return reactive refs or reactive objects [OK]

Common Mistakes:

• Returning plain variables instead of refs
• Not returning anything from the composable
• Using non-reactive variables inside composables

3. Given this Vue 3 setup using a composable:

import { ref } from 'vue';
function useToggle() {
  const isOn = ref(false);
  function toggle() { isOn.value = !isOn.value; }
  return { isOn, toggle };
}

const { isOn, toggle } = useToggle();
toggle();
toggle();
console.log(isOn.value);

What will be logged to the console?

medium

A. true

B. Error: isOn is not defined

C. undefined

D. false

Solution

1. Step 1: Trace the toggle function calls

   Initially, isOn.value is false. First toggle flips it to true, second toggle flips it back to false.

2. Step 2: Determine final value logged

   After two toggles, isOn.value is false, so console.log prints false.

3. Final Answer:

   false -> Option D

4. Quick Check:

   Two toggles flip false -> true -> false [OK]

Hint: Toggle flips boolean each call; two flips return to start [OK]

Common Mistakes:

• Assuming toggle only runs once
• Confusing ref.value with ref itself
• Expecting undefined or error due to scope confusion

4. This Vue 3 composable code has a bug:

import { ref } from 'vue';
function useCounter() {
  const count = ref(0);
  function increment() {
    count = count + 1;
  }
  return { count, increment };
}

What is the error and how to fix it?

medium

A. Missing return statement; fix by adding return count

B. Cannot reassign ref variable; fix by using count.value += 1

C. ref is not imported; fix by importing ref from 'vue'

D. increment function is not called; fix by calling increment() inside useCounter

Solution

1. Step 1: Identify the incorrect ref usage

   Ref variables are objects; you must update their .value property, not reassign the ref itself.

2. Step 2: Correct the increment function

   Change count = count + 1 to count.value += 1 to update the reactive value properly.

3. Final Answer:

   Cannot reassign ref variable; fix by using count.value += 1 -> Option B

4. Quick Check:

   Update ref.value, not ref itself [OK]

Hint: Update .value of ref, never reassign the ref variable [OK]

Common Mistakes:

• Reassigning the ref variable instead of its .value
• Forgetting to import ref
• Not returning reactive state from composable

5. You want to create a reusable composable that filters a list of items reactively based on a search term. Which advanced pattern best helps keep your Vue app clean and efficient?

hard

A. Use a composable with reactive refs for the list and search term, returning a computed filtered list.

B. Write the filtering logic directly inside each component's template using v-for and v-if.

C. Store the filtered list in a global variable outside Vue's reactivity system.

D. Use watchers to manually update the DOM elements for filtering.

Solution

1. Step 1: Identify the best pattern for reusable reactive filtering

   A composable with reactive refs and computed properties encapsulates logic cleanly and allows reuse.

2. Step 2: Evaluate other options for drawbacks

   Duplicating logic in templates, using non-reactive globals, or manual DOM updates are less efficient and clean.

3. Final Answer:

   Use a composable with reactive refs for the list and search term, returning a computed filtered list. -> Option A

4. Quick Check:

   Composable + reactive + computed = clean reusable filtering [OK]

Hint: Use composables with computed for reactive reusable logic [OK]

Common Mistakes:

• Duplicating filtering logic in templates
• Breaking reactivity by using global variables
• Manually manipulating DOM instead of reactive updates