Dependency injection in Express - Mini Project: Build & Apply

Dependency Injection in Express

📖 Scenario: You are building a simple Express server that needs to use a service for greeting users. To keep your code clean and testable, you will use dependency injection to provide the greeting service to your route handler.

🎯 Goal: Create an Express app that uses dependency injection to pass a greeting service to a route handler. The app will respond with a greeting message when a user visits the /greet endpoint.

📋 What You'll Learn

Create a greeting service function that returns a greeting string.

Create a configuration variable for the greeting message prefix.

Inject the greeting service into the Express route handler.

Set up the Express app to listen on port 3000.

💡 Why This Matters

🌍 Real World

Dependency injection helps keep Express apps modular and testable by separating service logic from route handlers.

💼 Career

Understanding dependency injection is important for writing clean, maintainable backend code in Node.js and Express, a common skill in web development jobs.

1

Create the greeting service function

Create a function called greetingService that takes a name parameter and returns the string `Hello, ${name}!`.

Express

// Your code here

Hint

Define a function that uses a template string to return a greeting.

2

Create a greeting prefix configuration variable

Create a constant called greetingPrefix and set it to the string 'Hello'.

Express

function greetingService(name) {
  return `Hello, ${name}!`;
}

// Your code here

Hint

Create a constant variable to hold the greeting prefix string.

3

Inject the greeting service into the Express route handler

Create an Express app by requiring express and calling express(). Then create a route handler for /greet that uses the injected greetingService to send a greeting for the query parameter name. Use req.query.name to get the name.

Express

function greetingService(name) {
  return `Hello, ${name}!`;
}

const greetingPrefix = 'Hello';

// Your code here

Hint

Use express() to create the app and define a GET route for /greet. Use the greeting service inside the route.

4

Start the Express server on port 3000

Add code to make the Express app listen on port 3000 using app.listen.

Express

const express = require('express');

function greetingService(name) {
  return `Hello, ${name}!`;
}

const greetingPrefix = 'Hello';

const app = express();

app.get('/greet', (req, res) => {
  const name = req.query.name || 'Guest';
  const message = greetingService(name);
  res.send(message);
});

// Your code here

Hint

Use app.listen(3000) to start the server on port 3000.

Practice

1. What is the main purpose of dependency injection in an Express app?

easy

A. To provide parts of the app with the resources they need without hardcoding them

B. To make the app run faster by caching data

C. To automatically generate routes based on file names

D. To handle errors globally in the app

Solution

1. Step 1: Understand dependency injection concept

   Dependency injection means giving parts of your app what they need instead of making them find it themselves.

2. Step 2: Identify the purpose in Express

   In Express, this helps keep code organized and flexible by passing dependencies explicitly.

3. Final Answer:

   To provide parts of the app with the resources they need without hardcoding them -> Option A

4. Quick Check:

   Dependency injection = Provide needed resources [OK]

Hint: Think: "Give what is needed, don't make it find" [OK]

Common Mistakes:

• Confusing dependency injection with caching
• Thinking it auto-generates routes
• Mixing it with error handling

2. Which of the following is the correct way to inject a service into an Express router?

easy

A. const router = express.Router(); router.use(service);

B. const router = express.Router(service);

C. function createRouter(service) { const router = express.Router(); router.service = service; return router; }

D. const router = express.Router(); router.service = service();

Solution

1. Step 1: Check how to pass dependencies in Express

   Express.Router() does not accept parameters directly, so passing service as argument is invalid.

2. Step 2: Use a factory function to inject service

   Creating a function that takes service and returns a router with service attached is the correct pattern.

3. Final Answer:

   function createRouter(service) { const router = express.Router(); router.service = service; return router; } -> Option C

4. Quick Check:

   Inject by factory function = function createRouter(service) { const router = express.Router(); router.service = service; return router; } [OK]

Hint: Use a function to pass dependencies, not Router constructor [OK]

Common Mistakes:

• Passing service directly to express.Router()
• Calling service as a middleware incorrectly
• Assigning service without a factory function

3. Consider this code snippet:

function createService() {
  return { getName: () => 'MyService' };
}

function createRouter(service) {
  const router = require('express').Router();
  router.get('/name', (req, res) => {
    res.send(service.getName());
  });
  return router;
}

const service = createService();
const router = createRouter(service);

// What happens when a GET request is made to '/name'?

medium

A. The server will crash due to missing middleware

B. The response will be undefined

C. There will be a runtime error because service is not defined

D. The response will be 'MyService'

Solution

1. Step 1: Analyze service creation

   The createService function returns an object with getName method returning 'MyService'.

2. Step 2: Analyze router handler

   The router uses the injected service and calls getName to send the response on '/name' route.

3. Final Answer:

   The response will be 'MyService' -> Option D

4. Quick Check:

   Injected service method returns 'MyService' [OK]

Hint: Injected service methods run as expected in route handlers [OK]

Common Mistakes:

• Assuming service is undefined inside handler
• Thinking service causes runtime error
• Confusing middleware with service injection

4. You have this code snippet:

function createRouter(service) {
  const router = require('express').Router();
  router.get('/data', (req, res) => {
    res.send(service.getData());
  });
  return router;
}

const router = createRouter();

What is the main issue here?

medium

A. The router is missing the service argument, causing service to be undefined

B. The router should be created with express() instead of express.Router()

C. The getData method is not defined on the router

D. The route path '/data' is invalid in Express

Solution

1. Step 1: Check function call for createRouter

   The createRouter function expects a service argument, but none is passed, so service is undefined.

2. Step 2: Understand impact on route handler

   Calling service.getData() will cause a runtime error because service is undefined.

3. Final Answer:

   The router is missing the service argument, causing service to be undefined -> Option A

4. Quick Check:

   Missing dependency argument = undefined service [OK]

Hint: Always pass dependencies when calling factory functions [OK]

Common Mistakes:

• Thinking express() should replace express.Router() here
• Confusing method definition with dependency injection
• Assuming route path is invalid

5. You want to inject a database client into multiple routers in your Express app. Which approach best supports this using dependency injection?

hard

A. Use a global variable for the database client and import it in each router file

B. Create a factory function for each router that accepts the database client and returns a configured router

C. Attach the database client directly to the Express app instance and access it via req.app

D. Create middleware that initializes the database client on every request

Solution

1. Step 1: Understand dependency injection best practice

   Injecting dependencies via factory functions keeps routers independent and testable.

2. Step 2: Evaluate options for injecting database client

   Factory functions allow passing the client explicitly to each router, avoiding globals and repeated initialization.

3. Final Answer:

   Create a factory function for each router that accepts the database client and returns a configured router -> Option B

4. Quick Check:

   Factory functions for injection = Create a factory function for each router that accepts the database client and returns a configured router [OK]

Hint: Use factory functions to pass shared resources cleanly [OK]

Common Mistakes:

• Using global variables which reduce testability
• Attaching client to app instance instead of injecting
• Initializing client on every request causing overhead