Why Dependency injection patterns in Vue? - Purpose & Use Cases

The Big Idea

Discover how to make your Vue components simpler and your app easier to change with one smart pattern!

The Scenario

Imagine building a Vue app where every component needs to create and manage its own data sources and services manually.

Each time you want to change a service, you have to update every component that uses it.

The Problem

This manual approach leads to repeated code, making your app hard to maintain and test.

It's easy to introduce bugs when you forget to update one component or when services depend on each other in complex ways.

The Solution

Dependency injection patterns let Vue components automatically receive the services they need without creating them directly.

This keeps your code clean, easy to update, and makes testing much simpler.

Before vs After

✗ Before

const service = new ApiService();
service.fetchData();

✓ After

const service = inject('apiService');
service.fetchData();

What It Enables

It enables building flexible, maintainable Vue apps where components focus on their job, not on managing dependencies.

Real Life Example

Think of a shopping cart component that needs a pricing service. With dependency injection, you can swap the pricing logic easily without changing the cart code.

Key Takeaways

Manual service creation causes repeated code and bugs.

Dependency injection provides services automatically to components.

This leads to cleaner, easier-to-maintain Vue applications.

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