Reactive objects with reactive in Vue - Performance & Optimization

Performance: Reactive objects with reactive

MEDIUM IMPACT

This affects how Vue tracks changes in objects and updates the DOM efficiently.

Tracking changes in a complex object to update UI

Vue

const state = reactive({ user: { name: 'Alice', age: 30 } });
// Use Vue's reactive system properly; mutations are tracked efficiently
state.user.name = 'Bob';

Vue's reactive system tracks nested changes efficiently with reactive objects, minimizing unnecessary updates.

📈 Performance GainSingle reactivity update triggers one DOM patch

Tracking changes in a complex object to update UI

Vue

const state = ref({ user: { name: 'Alice', age: 30 } });
// Directly mutating nested properties without reactivity helpers
state.value.user.name = 'Bob';

Mutating nested properties directly can cause Vue to track changes inefficiently if not handled carefully, leading to extra re-renders.

📉 Performance CostTriggers multiple reactivity checks and potentially multiple DOM updates

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Direct nested mutation without optimization	Multiple DOM updates	Multiple reflows	High paint cost	[X] Bad
Reactive object with minimal nested changes	Single DOM update	Single reflow	Low paint cost	[OK] Good

Rendering Pipeline

When a reactive object's property changes, Vue's reactivity system detects it and schedules a component update. This update triggers style recalculation, layout, paint, and composite steps in the browser.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout and Paint stages are most expensive due to DOM updates triggered by reactive changes.

Core Web Vital Affected

INP

This affects how Vue tracks changes in objects and updates the DOM efficiently.

Optimization Tips

1Use reactive() to track object changes efficiently.

2Avoid frequent deep nested mutations to reduce re-renders.

3Keep reactive objects as small and flat as possible.

Performance Quiz - 3 Questions

What is the main performance benefit of using Vue's reactive() for objects?

A It automatically batches all JavaScript code.

B It tracks nested property changes efficiently to minimize DOM updates.

C It prevents any DOM updates from happening.

D It increases the bundle size significantly.

DevTools: Performance

How to check: Record a performance profile while interacting with the component that uses reactive objects. Look for multiple layout or paint events triggered by reactive changes.

What to look for: Check if reactive changes cause multiple reflows or paints; fewer and shorter events indicate better performance.

Practice

1. What does the reactive function in Vue do?

easy

A. It converts a reactive object into a plain JavaScript object.

B. It makes an object reactive so Vue tracks its changes automatically.

C. It creates a new Vue component.

D. It registers a global event listener.

Solution

1. Step 1: Understand the purpose of reactive

   The reactive function wraps an object so Vue can track its property changes.

2. Step 2: Compare options with the purpose

   Only It makes an object reactive so Vue tracks its changes automatically. correctly describes this behavior; others describe unrelated Vue features.

3. Final Answer:

   It makes an object reactive so Vue tracks its changes automatically. -> Option B

4. Quick Check:

   reactive() tracks object changes = C [OK]

Hint: Remember: reactive() wraps objects to track changes [OK]

Common Mistakes:

• Confusing reactive() with component creation
• Thinking reactive() converts reactive objects back to plain objects
• Assuming reactive() adds event listeners

2. Which of the following is the correct way to create a reactive object in Vue 3?

easy

A. const state = reactive.count = 0

B. const state = reactive = { count: 0 }

C. const state = reactive([count: 0])

D. const state = reactive({ count: 0 })

Solution

1. Step 1: Check the syntax for reactive object creation

   The correct syntax is calling reactive() with an object: reactive({ count: 0 }).

2. Step 2: Identify syntax errors in other options

   const state = reactive = { count: 0 } uses invalid assignment, C uses array syntax incorrectly, D tries to assign property directly without reactive call.

3. Final Answer:

   const state = reactive({ count: 0 }) -> Option D

4. Quick Check:

   reactive() called with object literal = A [OK]

Hint: Use reactive() with an object inside parentheses [OK]

Common Mistakes:

• Using assignment instead of function call
• Passing array instead of object
• Assigning properties outside reactive()

3. Given this code, what will be logged to the console?

import { reactive } from 'vue'
const state = reactive({ count: 1 })
state.count = 5
console.log(state.count)

medium

A. 5

B. Error: Cannot assign to reactive property

C. undefined

D. 1

Solution

1. Step 1: Understand reactive object property update

   Assigning state.count = 5 updates the reactive property value.

2. Step 2: Check the logged value

   Logging state.count after update outputs the new value 5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Updated reactive property logs new value = D [OK]

Hint: Reactive objects update properties directly and reflect changes [OK]

Common Mistakes:

• Thinking reactive objects are immutable
• Expecting old value after update
• Confusing reactive with ref syntax

4. What is wrong with this Vue 3 code snippet?

import { reactive } from 'vue'
const state = reactive({ count: 0 })
state = { count: 5 }

medium

A. You cannot reassign a reactive object variable directly.

B. The reactive function requires an array, not an object.

C. The property count must be declared with ref(), not reactive.

D. Reactive objects cannot have numeric properties.

Solution

1. Step 1: Identify the error in variable reassignment

   The variable state is declared with const, so it cannot be reassigned.

2. Step 2: Understand reactive object usage

   Reactive objects are mutable in their properties but the variable holding them cannot be reassigned if declared const.

3. Final Answer:

   You cannot reassign a reactive object variable directly. -> Option A

4. Quick Check:

   const variable reassignment causes error = A [OK]

Hint: const variables can't be reassigned, only their properties changed [OK]

Common Mistakes:

• Trying to reassign const reactive variables
• Confusing reactive() input types
• Thinking reactive objects restrict property types

5. You want to create a reactive object to track a user's profile with nested address info. Which code correctly makes the entire object reactive so changes to nested properties update the UI?

hard

A. const profile = reactive({ name: 'Alice' }); profile.address = { city: 'NY', zip: '10001' }

B. const profile = { name: 'Alice', address: reactive({ city: 'NY', zip: '10001' }) }

C. const profile = reactive({ name: 'Alice', address: { city: 'NY', zip: '10001' } })

D. const profile = reactive({ name: 'Alice', address: ref({ city: 'NY', zip: '10001' }) })

Solution

1. Step 1: Understand nested reactivity with reactive()

   Using reactive() on the whole object recursively makes nested properties reactive automatically.

2. Step 2: Analyze each option's approach

   const profile = reactive({ name: 'Alice', address: { city: 'NY', zip: '10001' } }) wraps the entire object including nested address, so all changes are reactive. const profile = reactive({ name: 'Alice' }); profile.address = { city: 'NY', zip: '10001' } assigns a plain object to nested property after reactive call, losing reactivity for nested changes. const profile = { name: 'Alice', address: reactive({ city: 'NY', zip: '10001' }) } mixes reactive inside plain object, which breaks reactivity tracking. const profile = reactive({ name: 'Alice', address: ref({ city: 'NY', zip: '10001' }) }) mixes ref inside reactive, which is invalid since reactive expects plain objects.

3. Final Answer:

   const profile = reactive({ name: 'Alice', address: { city: 'NY', zip: '10001' } }) -> Option C

4. Quick Check:

   reactive() wraps whole nested object = B [OK]

Hint: Wrap entire nested object with reactive() for full reactivity [OK]

Common Mistakes:

• Wrapping nested objects separately after reactive() call
• Mixing reactive and plain objects incorrectly
• Assigning plain objects to reactive properties