Dependency injection patterns in Vue - Performance & Optimization

Performance: Dependency injection patterns

MEDIUM IMPACT

This affects the initial load time and runtime responsiveness by controlling how dependencies are created and shared in Vue components.

Sharing a service instance across multiple components

Vue

import { provide, inject, reactive } from 'vue';

// In a parent or root component
export default {
  setup() {
    const service = reactive({ count: 0 });
    provide('service', service);
    return {};
  }
}

// In child components
export default {
  setup() {
    const service = inject('service');
    return { service };
  }
}

Provides a single shared reactive service instance to all child components, reducing memory and improving state consistency.

📈 Performance GainSaves memory and improves INP by avoiding redundant reactive object creation.

Sharing a service instance across multiple components

Vue

import { reactive } from 'vue';

export default {
  setup() {
    const service = reactive({ count: 0 });
    // Each component creates its own service instance
    return { service };
  }
}

Each component creates a new service instance causing redundant memory use and inconsistent state.

📉 Performance CostIncreases memory usage and can cause slower interaction responsiveness due to duplicated state management.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Creating new service instance per component	None	0	Low but repeated JS execution	[X] Bad
Using provide/inject to share service instance	None	0	Low JS execution once	[OK] Good

Rendering Pipeline

Dependency injection affects the setup phase of Vue components, influencing how reactive dependencies are created and shared before rendering.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution during component setup if dependencies are created repeatedly or inefficiently.

Core Web Vital Affected

INP

This affects the initial load time and runtime responsiveness by controlling how dependencies are created and shared in Vue components.

Optimization Tips

1Use provide/inject to share dependencies and avoid redundant creation.

2Initialize heavy dependencies once to prevent blocking rendering.

3Avoid creating reactive objects repeatedly in multiple components.

Performance Quiz - 3 Questions

What is a performance benefit of using provide/inject for dependency injection in Vue?

A It shares a single instance to avoid repeated heavy initialization.

B It forces each component to create its own instance for isolation.

C It delays rendering until all dependencies are fetched from the server.

D It automatically caches DOM nodes to reduce reflows.

DevTools: Performance

How to check: Record a performance profile while loading the page and interacting with components. Look for long scripting tasks during component setup.

What to look for: Check if heavy initialization runs multiple times or if shared dependencies reduce scripting time and improve interaction responsiveness.

Practice

1. What is the main purpose of using provide and inject in Vue?

easy

A. To define routes in a Vue application

B. To share data or functions between components without passing props manually

C. To handle component lifecycle hooks

D. To create global CSS styles for components

Solution

1. Step 1: Understand the role of provide/inject

   They allow sharing data or functions from a parent component to its descendants without passing props through every intermediate component.

2. Step 2: Compare with other options

   The other options relate to defining routes, creating global CSS styles, and handling component lifecycle hooks, which are unrelated to provide/inject.

3. Final Answer:

   To share data or functions between components without passing props manually -> Option B

4. Quick Check:

   Dependency injection = share data without props [OK]

Hint: Remember provide/inject shares data without prop drilling [OK]

Common Mistakes:

• Confusing provide/inject with props or events
• Thinking provide/inject manages styles or routing
• Assuming provide/inject replaces Vuex or global state

2. Which of the following is the correct syntax to provide a value in a Vue 3 component using the Composition API?

easy

A. const value = inject('key')

B. this.provide('key', value)

C. provide('key', value)

D. inject('key', value)

Solution

1. Step 1: Identify provide syntax in Composition API

   In Vue 3 Composition API, you call provide('key', value) inside setup() to share data.

2. Step 2: Check other options

   const value = inject('key') is for injection, not providing. this.provide('key', value) uses this which is not used in setup(). inject('key', value) is incorrect because inject does not provide values.

3. Final Answer:

   provide('key', value) -> Option C

4. Quick Check:

   Provide = provide('key', value) [OK]

Hint: Provide uses provide('key', value) inside setup() [OK]

Common Mistakes:

• Using inject instead of provide to share data
• Trying to call provide on this inside setup()
• Confusing provide syntax with options API methods

3. Given the following Vue 3 setup, what will be logged in the child component?

import { provide, inject } from 'vue';
const Parent = {
  setup() {
    provide('message', 'Hello from parent')
  }
}

const Child = {
  setup() {
    const msg = inject('message')
    console.log(msg)
  }
}

medium

A. null

B. undefined

C. An error because provide is missing a return

D. 'Hello from parent'

Solution

1. Step 1: Understand provide/inject behavior

   The parent provides the string 'Hello from parent' with key 'message'. The child injects this key and receives the value.

2. Step 2: Predict console output

   Since the child injects the provided key correctly, it logs 'Hello from parent'.

3. Final Answer:

   'Hello from parent' -> Option D

4. Quick Check:

   Inject returns provided value = 'Hello from parent' [OK]

Hint: Inject returns what provide shares by key [OK]

Common Mistakes:

• Expecting undefined if no return in setup
• Confusing provide with returning values
• Assuming inject returns null if key exists

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

import { provide, inject } from 'vue';
const Parent = {
  setup() {
    provide('data', 123)
  }
}

const Child = {
  setup() {
    const data = inject('data')
    console.log(data)
  }
}

medium

A. inject is missing a default value, may cause undefined

B. provide is called outside setup()

C. provide must return an object

D. inject cannot be used in setup()

Solution

1. Step 1: Check provide usage

   Provide is correctly called inside setup() with key 'data' and value 123.

2. Step 2: Check inject usage

   Inject is called correctly but without a default value. If the key is missing, it returns undefined, which might cause issues.

3. Final Answer:

   inject is missing a default value, may cause undefined -> Option A

4. Quick Check:

   Inject without default can be undefined [OK]

Hint: Always provide default value to inject to avoid undefined [OK]

Common Mistakes:

• Thinking provide must return an object
• Believing inject can't be used in setup
• Assuming provide is outside setup here

5. You want to share a reactive object between a grandparent and a grandchild component using provide/inject in Vue 3. Which approach correctly ensures the grandchild reacts to changes in the shared object?

hard

A. Provide a reactive object using provide('state', reactiveObj) and inject it normally in the grandchild

B. Provide a plain object and inject it with a default value in the grandchild

C. Provide a reactive object but inject it inside onMounted hook in the grandchild

D. Provide a reactive object but convert it to a ref before injecting

Solution

1. Step 1: Understand reactive sharing with provide/inject

   Providing a reactive object directly shares its reactivity, so descendants see updates.

2. Step 2: Evaluate options for reactivity

   Provide a reactive object using provide('state', reactiveObj) and inject it normally in the grandchild correctly provides a reactive object and injects it normally, preserving reactivity. Provide a plain object and inject it with a default value in the grandchild uses a plain object, losing reactivity. Provide a reactive object but inject it inside onMounted hook in the grandchild delays injection unnecessarily. Provide a reactive object but convert it to a ref before injecting converts reactive to ref, which is unnecessary and may cause confusion.

3. Final Answer:

   Provide a reactive object using provide('state', reactiveObj) and inject it normally in the grandchild -> Option A

4. Quick Check:

   Reactive object provided and injected keeps reactivity [OK]

Hint: Provide reactive object directly to keep reactivity in inject [OK]

Common Mistakes:

• Providing plain objects losing reactivity
• Injecting inside lifecycle hooks unnecessarily
• Converting reactive to ref before injecting