Props drilling problem in Vue - Performance & Optimization

Performance: Props drilling problem

MEDIUM IMPACT

This affects the rendering speed and responsiveness by increasing the number of component updates and re-renders due to passing props through many layers.

Passing data from a top-level component to a deeply nested child component

Vue

<Parent>
  <Child1 />
</Parent>

// Use provide/inject or a global store to share data directly with Child3 without passing through Child1 and Child2

By using provide/inject or a store, only the components that need the data re-render, reducing unnecessary updates.

📈 Performance GainReduces re-renders and prop updates to only relevant components, improving INP and lowering CPU load.

Passing data from a top-level component to a deeply nested child component

Vue

<Parent>
  <Child1 :data="data">
    <Child2 :data="data">
      <Child3 :data="data" />
    </Child2>
  </Child1>
</Parent>

Each intermediate component must receive and pass down props even if they don't use them, causing unnecessary re-renders and prop updates.

📉 Performance CostTriggers multiple re-renders and prop updates across all intermediate components, increasing INP and CPU usage.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Props drilling through many components	Many components receive and pass props	Multiple reflows triggered by each re-render	High paint cost due to repeated updates	[X] Bad
Using provide/inject or global store	Only components that consume data update	Single or minimal reflows triggered	Lower paint cost due to fewer updates	[OK] Good

Rendering Pipeline

Props drilling causes many components to receive new props and re-render, triggering multiple layout recalculations and paints.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution and Layout due to repeated re-renders of intermediate components

Core Web Vital Affected

INP

This affects the rendering speed and responsiveness by increasing the number of component updates and re-renders due to passing props through many layers.

Optimization Tips

1Avoid passing props through components that don't need them.

2Use provide/inject or a global store to share data with deeply nested components.

3Fewer re-renders mean better interaction responsiveness (INP).

Performance Quiz - 3 Questions

What is the main performance problem caused by props drilling in Vue?

A Excessive CSS recalculations

B Too many DOM nodes created

C Unnecessary re-renders of intermediate components

D Blocking network requests

DevTools: Performance

How to check: Record a performance profile while interacting with the app. Look for many component re-renders and long scripting times related to prop updates.

What to look for: High scripting time and many repeated component renders indicate props drilling issues.

Practice

1. What is props drilling in Vue?

easy

A. Using Vuex store to manage state globally

B. Passing props through many nested components to reach a child

C. Directly modifying props inside a child component

D. Using props only in the root component

Solution

1. Step 1: Understand props usage in Vue

   Props are used to pass data from parent to child components.

2. Step 2: Define props drilling

   Props drilling happens when you pass props through many layers of components just to reach a deeply nested child.

3. Final Answer:

   Passing props through many nested components to reach a child -> Option B

4. Quick Check:

   Props drilling = Passing props through many layers [OK]

Hint: Props drilling means many layers pass props down [OK]

Common Mistakes:

• Thinking props drilling means using props only at root
• Confusing props drilling with modifying props in child
• Mixing props drilling with global state management

2. Which of the following is the correct way to pass a prop named title from a parent to a child component in Vue?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recognize Vue prop binding syntax

   Props can be passed using shorthand : or full v-bind: syntax.

2. Step 2: Compare options

   uses shorthand :, uses v-bind:. Both correctly bind the variable parentTitle as a prop.

3. Final Answer:

   Both A and C -> Option A

4. Quick Check:

   Use : or v-bind: for dynamic props [OK]

Hint: Use : or v-bind: to pass dynamic props [OK]

Common Mistakes:

• Passing prop as plain string without binding
• Confusing attribute with prop binding
• Using incorrect syntax like

3. Given this component structure:
App -> Parent -> Child
and App passes a prop message to Parent, which passes it to Child. What will Child display if message is "Hello"?

<template>
  <div>{{ message }}</div>
</template>

<script setup>
defineProps(['message'])
</script>

medium

A. Hello

B. undefined

C. Error: message not defined

D. Empty string

Solution

1. Step 1: Trace prop passing

   App passes message="Hello" to Parent, Parent passes it to Child as prop.

2. Step 2: Child uses message prop correctly

   Child receives message prop and displays it inside the div.

3. Final Answer:

   Hello -> Option A

4. Quick Check:

   Prop passed down correctly = Hello [OK]

Hint: If prop passed correctly, child shows its value [OK]

Common Mistakes:

• Forgetting to pass prop from Parent to Child
• Not defining props in Child component
• Expecting prop to be reactive without passing

4. In a Vue app, you pass a prop user from App to Parent and then to Child. You get an error: Property 'user' is not defined in Child. What is the likely cause?

medium

A. All of the above

B. Parent component did not pass user prop to Child

C. Child component did not declare user in defineProps

D. App did not pass user prop to Parent

Solution

1. Step 1: Analyze the error message

   The error Property 'user' is not defined occurs when accessing a prop in the template without declaring it in defineProps in the Child.

2. Step 2: Distinguish from other issues

   If declared but not passed from Parent or App, the prop would be undefined, not trigger this specific error.

3. Final Answer:

   Child component did not declare user in defineProps -> Option C

4. Quick Check:

   'Property not defined' = missing defineProps declaration [OK]

Hint: 'Property not defined' means missing defineProps in child [OK]

Common Mistakes:

• Assuming props auto-pass without explicit binding
• Not declaring props in child component
• Ignoring error messages about undefined props

5. You want to avoid props drilling for a deeply nested component needing user data. Which Vue feature helps reduce props drilling?

hard

A. Using multiple emits to send data back up

B. Passing props through every intermediate component

C. Using local component state only

D. Using provide/inject to share data between ancestor and descendant

Solution

1. Step 1: Understand props drilling problem

   Passing props through many layers is tedious and hard to maintain.

2. Step 2: Identify Vue feature to avoid drilling

   Vue's provide/inject allows ancestor components to share data directly with descendants without passing props through every layer.

3. Final Answer:

   Using provide/inject to share data between ancestor and descendant -> Option D

4. Quick Check:

   Provide/inject reduces props drilling [OK]

Hint: Use provide/inject to skip intermediate props [OK]

Common Mistakes:

• Thinking local state shares data globally
• Using emits to send data down instead of up
• Passing props through every layer instead of provide/inject