Why component patterns matter in Vue - Performance Evidence

Performance: Why component patterns matter

HIGH IMPACT

This affects how fast the page loads and how smoothly the app responds to user actions by controlling rendering and updates.

Building a Vue app with reusable components

Vue

<script setup>
const items = ref(Array(1000).fill(0))
</script>
<template>
  <div>
    <ItemComponent v-for="(item, index) in items" :key="index" :item="item" />
  </div>
</template>

<script>
export default {
  props: ['item'],
  setup() {
    // use shallow reactive or memoized computed to avoid unnecessary updates
  }
}
</script>

Memoizing and limiting reactive dependencies reduces re-renders to only changed items.

📈 Performance GainReduces re-renders from 1000 to only changed items, improving interaction responsiveness.

Building a Vue app with reusable components

Vue

<script setup>
const items = ref(Array(1000).fill(0))
</script>
<template>
  <div>
    <ItemComponent v-for="(item, index) in items" :key="index" :item="item" />
  </div>
</template>

<script>
export default {
  props: ['item'],
  setup() {
    // heavy computed or watchers inside each item
  }
}
</script>

Each item component does heavy work and re-renders unnecessarily, causing slow updates and lag.

📉 Performance CostTriggers 1000 re-renders on small data changes, blocking interaction for hundreds of milliseconds.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy reactive dependencies in many child components	High (many nodes updated)	High (many reflows)	High (many paints)	[X] Bad
Memoized props and shallow reactive data	Low (only changed nodes)	Low (few reflows)	Low (minimal paints)	[OK] Good

Rendering Pipeline

Component patterns affect how Vue tracks reactive data and triggers updates, influencing style calculation, layout, and paint.

→Reactive Dependency Tracking

→Virtual DOM Diffing

→Layout

→Paint

⚠️ BottleneckExcessive reactive updates cause repeated Virtual DOM diffing and layout recalculations.

Core Web Vital Affected

INP

This affects how fast the page loads and how smoothly the app responds to user actions by controlling rendering and updates.

Optimization Tips

1Avoid heavy reactive dependencies inside many child components.

2Use memoization and shallow reactive data to limit updates.

3Always provide stable keys for list rendering to optimize diffing.

Performance Quiz - 3 Questions

What is a main performance risk of poorly designed Vue component patterns?

A Using too many CSS classes

B Excessive component re-renders causing slow interaction

C Too few components causing large DOM trees

D Not using Vue Router

DevTools: Performance

How to check: Record a performance profile while interacting with the component, then analyze the flame chart for excessive component updates and layout recalculations.

What to look for: Look for many repeated component renders and layout thrashing indicating inefficient component patterns.

Practice

1. Why is it important to use component patterns in Vue applications?

easy

A. They slow down the app performance

B. They make code easier to read and reuse

C. They increase the file size unnecessarily

D. They prevent the use of props

Solution

1. Step 1: Understand the role of component patterns

   Component patterns organize code into reusable parts, making it easier to manage.

2. Step 2: Identify the benefit of reusability and readability

   Using patterns helps developers read and reuse code efficiently, improving teamwork and maintenance.

3. Final Answer:

   They make code easier to read and reuse -> Option B

4. Quick Check:

   Component patterns = easier code reuse [OK]

Hint: Think about how patterns help reuse code [OK]

Common Mistakes:

• Confusing patterns with performance issues
• Assuming patterns increase file size
• Believing patterns restrict props usage

2. Which of the following is the correct way to define a simple Vue component using the Composition API?

easy

A. export default { setup: () => { count: 0 } }

B. export default function setup() { return { count: 0 } }

C. export default { setup() { return { count: 0 } } }

D. export default { data() { return { count: 0 } } }

Solution

1. Step 1: Recall Composition API syntax

   The setup() function is defined inside the component object and returns reactive state.

2. Step 2: Check each option's syntax

   export default { setup() { return { count: 0 } } } correctly defines setup() returning an object. export default function setup() { return { count: 0 } } is invalid syntax. export default { data() { return { count: 0 } } } uses Options API, not Composition API. export default { setup: () => { count: 0 } } has incorrect arrow function syntax.

3. Final Answer:

   export default { setup() { return { count: 0 } } } -> Option C

4. Quick Check:

   Correct setup() syntax = export default { setup() { return { count: 0 } } } [OK]

Hint: Remember setup() returns state object in Composition API [OK]

Common Mistakes:

• Confusing Options API with Composition API syntax
• Using arrow functions incorrectly in setup
• Not returning an object from setup

3. Given this Vue component code using a pattern for props and emits:

export default {
  props: { count: Number },
  emits: ['increment'],
  setup(props, { emit }) {
    function add() { emit('increment') }
    return { add }
  }
}

What happens when the add function is called?

medium

A. It emits an 'increment' event to the parent component

B. It changes the value of the count prop directly

C. It throws an error because emit is undefined

D. It updates the local count state automatically

Solution

1. Step 1: Understand the emit function in setup()

   The emit function sends events from child to parent components in Vue.

2. Step 2: Analyze the add() function behavior

   Calling add() triggers emit('increment'), which sends the 'increment' event upward.

3. Final Answer:

   It emits an 'increment' event to the parent component -> Option A

4. Quick Check:

   emit('increment') sends event [OK]

Hint: emit() sends events to parent components [OK]

Common Mistakes:

• Thinking props can be changed directly
• Assuming emit is undefined in setup
• Believing local state updates automatically

4. This Vue component code has an error:

import { ref } from 'vue';
export default {
  setup() {
    const count = ref(0)
    function increment() {
      count++
    }
    return { count, increment }
  }
}

What is the error and how to fix it?

medium

A. increment should be an arrow function

B. ref is not imported, so import it from 'vue'

C. setup must return a function, not an object

D. count is a ref, so use count.value++ instead of count++

Solution

1. Step 1: Identify how to update a ref value

   Refs hold values inside .value property, so count++ is invalid.

2. Step 2: Correct the increment function

   Use count.value++ to update the reactive ref correctly.

3. Final Answer:

   count is a ref, so use count.value++ instead of count++ -> Option D

4. Quick Check:

   Update ref with .value [OK]

Hint: Update ref values with .value [OK]

Common Mistakes:

• Trying to increment ref directly
• Forgetting to import ref (though not asked here)
• Thinking setup returns a function

5. You want to create a reusable Vue component pattern that accepts a list of items and emits an event when an item is selected. Which pattern best supports this goal?

hard

A. Use props to pass the list and emits to notify selection

B. Use local data to store the list and watch to detect selection

C. Use global variables to share the list and methods to select

D. Use slots to pass the list and computed properties to emit

Solution

1. Step 1: Identify how to pass data into components

   Props are the standard way to pass data like lists into Vue components.

2. Step 2: Identify how to notify parent components

   Emits are used to send events like item selection back to the parent.

3. Step 3: Evaluate other options

   Local data won't receive external lists. Global variables break encapsulation. Slots are for content, not data lists. Computed properties don't emit events.

4. Final Answer:

   Use props to pass the list and emits to notify selection -> Option A

5. Quick Check:

   Props in, emits out = reusable pattern [OK]

Hint: Props in, emits out for reusable components [OK]

Common Mistakes:

• Using local data instead of props for input
• Relying on global variables for data sharing
• Misusing slots for data passing