Dependency injection patterns in Vue - Step-by-Step Execution

Concept Flow - Dependency injection patterns

Create Provider Component

↓

Define Provide Key & Value

↓

Child Component Requests Injection

↓

Inject Value Using Key

↓

Use Injected Value in Child

↓

Render Child with Dependency

Shows how a parent component provides a value that child components inject and use.

Execution Sample

Vue

import { provide, inject } from 'vue';

// Parent component
export default {
  setup() {
    provide('color', 'blue');
  }
};

// Child component
export default {
  setup() {
    const color = inject('color');
    return { color };
  }
};

Parent provides a 'color' value, child injects and uses it.

Execution Table

Step	Action	Component	Provide/Inject Key	Value	Result
1	Parent setup runs	Parent	color	blue	Value 'blue' provided under key 'color'
2	Child setup runs	Child	color	-	Child requests injection of 'color'
3	Injection resolved	Child	color	blue	Child receives value 'blue'
4	Child uses value	Child	-	blue	Child renders using injected 'blue'
5	Render complete	Both	-	-	Child shows color 'blue' from injection

💡 Injection completes when child receives provided value and renders

Variable Tracker

Variable	Parent Setup	Child Setup	After Injection	Final
providedValue	blue	blue	blue	blue
injectedValue	-	undefined	blue	blue

Key Moments - 3 Insights

Why does the child get 'undefined' before injection?

Before injection (see execution_table step 2), the child has no value until inject() resolves it in step 3.

Can the child inject a key not provided by the parent?

No, if the parent does not provide a key, inject() returns undefined or a default value (not shown here).

Does provide() create reactive bindings automatically?

No, provide() passes the value as is; to make it reactive, you must provide reactive objects explicitly.

Visual Quiz - 3 Questions

Look at the execution_table, what value does the child receive at step 3?

A undefined

B 'color'

C 'blue'

D null

💡 Hint

Check the 'Value' column at step 3 in the execution_table.

At which step does the child request the injected value?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look for 'Child requests injection' in the 'Action' column.

If the parent did not provide 'color', what would the child receive?

A undefined

B 'blue'

C null

D an error

💡 Hint

Recall the key_moments about missing provide keys and inject() behavior.

Concept Snapshot

Dependency Injection in Vue:
- Parent uses provide(key, value) in setup()
- Child uses inject(key) in setup() to access value
- Injected values are passed down the component tree
- If no provider, inject returns undefined or default
- Reactive values must be explicitly provided
- Enables loose coupling and easier testing

Full Transcript

Dependency injection in Vue works by having a parent component provide a value with a key using the provide() function inside its setup. Child components can then request this value by calling inject() with the same key inside their setup. The process starts with the parent providing the value, then the child requesting it, receiving it, and finally using it in rendering. If the child tries to inject a key that the parent did not provide, it will get undefined. Also, provide does not automatically make values reactive; you must provide reactive objects explicitly. This pattern helps components share data without tight coupling.

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