How Vue tracks dependencies automatically - Performance Optimization Steps

Performance: How Vue tracks dependencies automatically

MEDIUM IMPACT

This affects how efficiently Vue updates the UI by tracking which parts of the data each component uses, minimizing unnecessary work.

Updating UI only when relevant data changes

Vue

const state = reactive({ count: 0, name: 'Vue' });
watchEffect(() => {
  console.log(state.count);
});
// Vue tracks only 'count' dependency, ignoring 'name' changes.

Only the used reactive properties trigger updates, reducing unnecessary work.

📈 Performance Gainreduces reflows and repaints to only when relevant data changes

Updating UI only when relevant data changes

Vue

const state = reactive({ count: 0, name: 'Vue' });
watchEffect(() => {
  console.log(state.count, state.name);
});
// This logs whenever any reactive property changes, even if only one is needed.

Tracking all properties causes more updates than needed, triggering extra re-renders.

📉 Performance Costtriggers multiple reflows and repaints per unrelated data change

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Tracking all reactive properties regardless of usage	High (many updates)	Multiple per unrelated change	High (many repaints)	[X] Bad
Tracking only accessed reactive properties automatically	Low (targeted updates)	Single per relevant change	Low (minimal repaints)	[OK] Good

Rendering Pipeline

Vue's reactive system intercepts property access during rendering to record dependencies. When data changes, only components depending on that data re-run their render functions, minimizing layout and paint work.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout and Paint caused by unnecessary component updates

Core Web Vital Affected

INP

This affects how efficiently Vue updates the UI by tracking which parts of the data each component uses, minimizing unnecessary work.

Optimization Tips

1Vue tracks reactive property access during rendering to know what to update.

2Only components using changed data re-render, saving layout and paint work.

3Avoid accessing unused reactive properties to prevent extra updates.

Performance Quiz - 3 Questions

What does Vue's automatic dependency tracking help reduce?

A Unnecessary component updates and re-renders

B The size of the JavaScript bundle

C The number of HTTP requests

D The initial page load time

DevTools: Performance

How to check: Record a performance profile while interacting with your Vue app. Look for unnecessary component re-renders or layout recalculations.

What to look for: Check if components re-render only when their reactive dependencies change, indicated by fewer layout and paint events.

Practice

1. How does Vue automatically know which parts of your app to update when data changes?

easy

A. Vue updates everything on the page every time any data changes.

B. You must manually list all variables Vue should watch for changes.

C. Vue uses a timer to check for changes every second.

D. Vue tracks reactive data dependencies during rendering using ref and computed.

Solution

1. Step 1: Understand Vue's reactive system

   Vue uses special reactive data wrappers like ref and computed to track dependencies automatically.

2. Step 2: How Vue tracks dependencies

   When rendering, Vue records which reactive data is accessed, so it knows what to update when data changes.

3. Final Answer:

   Vue tracks reactive data dependencies during rendering using ref and computed. -> Option D

4. Quick Check:

   Automatic dependency tracking = Vue tracks reactive data dependencies during rendering using ref and computed. [OK]

Hint: Vue tracks reactive data accessed during rendering [OK]

Common Mistakes:

• Thinking you must manually specify dependencies
• Believing Vue updates everything on any change
• Assuming Vue uses timers to detect changes

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

easy

A. const count = reactive(0);

B. const count = ref(0);

C. const count = computed(0);

D. const count = watch(0);

Solution

1. Step 1: Identify the correct reactive API

   In Vue 3, ref is used to create a reactive reference to a primitive value like a number.

2. Step 2: Check other options

   reactive is for objects, computed creates derived values, and watch observes changes but does not create reactive data.

3. Final Answer:

   const count = ref(0); -> Option B

4. Quick Check:

   Reactive primitive = ref() = const count = ref(0); [OK]

Hint: Use ref() for reactive primitives in Vue 3 [OK]

Common Mistakes:

• Using reactive() for primitive values
• Confusing computed() with ref()
• Trying to use watch() to create reactive data

3. Consider this Vue 3 code:

const count = ref(0);
const double = computed(() => count.value * 2);

console.log(double.value);
count.value = 5;
console.log(double.value);

What will be printed in the console?

medium

A. 0 and 10

B. 0 and 0

C. NaN and 10

D. 5 and 10

Solution

1. Step 1: Initial value of count and double

   Initially, count.value is 0, so double.value is 0 * 2 = 0.

2. Step 2: After updating count

   When count.value changes to 5, double automatically recalculates to 5 * 2 = 10.

3. Final Answer:

   0 and 10 -> Option A

4. Quick Check:

   Computed updates with reactive changes = 0 and 10 [OK]

Hint: Computed updates automatically when dependencies change [OK]

Common Mistakes:

• Expecting double to stay 0 after count changes
• Confusing initial and updated values
• Not accessing .value on refs

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

const count = ref(0);
const double = computed(() => count * 2);

console.log(double.value);

medium

A. computed cannot be used with ref values.

B. ref should be reactive instead.

C. You must use count.value inside computed, not count directly.

D. You need to call double() instead of double.value.

Solution

1. Step 1: Check how ref is accessed inside computed

   Refs store their value inside a .value property, so you must use count.value to get the number.

2. Step 2: Identify the error

   The code uses count directly, which is a ref object, not the number, causing wrong behavior.

3. Final Answer:

   You must use count.value inside computed, not count directly. -> Option C

4. Quick Check:

   Access ref with .value inside computed = You must use count.value inside computed, not count directly. [OK]

Hint: Always use .value to access ref inside computed [OK]

Common Mistakes:

• Using ref variable directly without .value
• Thinking computed can't use ref
• Calling computed like a function instead of .value

5. You want to create a Vue 3 component that shows a list of items and a count of how many items have a price over 10. Which approach correctly uses Vue's automatic dependency tracking?

hard

A. Use a computed property that filters the reactive items array and returns the count of items with price > 10.

B. Manually watch the items array and update a separate count variable whenever items change.

C. Use a method that counts items with price > 10 and call it only once on component mount.

D. Store the count as a normal variable and update it inside the template.

Solution

1. Step 1: Understand reactive data and computed

   A reactive array wrapped with ref or reactive can be used inside a computed property to automatically track dependencies.

2. Step 2: Why computed is best here

   The computed property recalculates the count whenever the items array changes, so the UI stays updated without manual intervention.

3. Final Answer:

   Use a computed property that filters the reactive items array and returns the count of items with price > 10. -> Option A

4. Quick Check:

   Computed auto-updates with reactive data = Use a computed property that filters the reactive items array and returns the count of items with price > 10. [OK]

Hint: Use computed to auto-update counts from reactive arrays [OK]

Common Mistakes:

• Manually watching and updating counts instead of computed
• Using methods that don't auto-update
• Trying to update counts inside template variables