Dependency injection in Express - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import Express and create an app instance.

Express

const express = require('[1]');
const app = express();

Drag options to blanks, or click blank then click option'

Apath

Bhttp

Cfs

Dexpress

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'http' instead of 'express' to import Express.

Forgetting to require the module before using it.

The Express library is imported by requiring 'express'. This creates the Express module needed to create the app.

2fill in blank

medium

Complete the code to inject a dependency into a route handler using Express's request object.

Express

app.get('/greet', (req, res) => {
  const greeter = req.[1].greeter;
  res.send(greeter.greet());
});

Drag options to blanks, or click blank then click option'

Aparams

Bbody

Ccontainer

Dquery

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'req.body' which holds POST data, not dependencies.

Using 'req.params' or 'req.query' which hold URL parameters.

Dependency injection can be done by attaching dependencies to a custom property on the request object, often named 'container' or similar.

3fill in blank

hard

Fix the error in the middleware that injects a service into the request object.

Express

function injectService(req, res, next) {
  req.[1] = { greeter: { greet: () => 'Hello!' } };
  next();
}

Drag options to blanks, or click blank then click option'

Acontainer

Binject

Cservices

Dservice

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent property names causing undefined errors.

Not calling next() to pass control to the next middleware.

Using 'req.container' is a common pattern to hold injected dependencies in Express middleware.

4fill in blank

hard

Fill both blanks to create middleware that injects a logger service and use it in a route.

Express

function injectLogger(req, res, next) {
  req.[1] = { log: (msg) => console.log(msg) };
  next();
}

app.get('/log', (req, res) => {
  req.[2].log('Logging a message');
  res.send('Logged');
});

Drag options to blanks, or click blank then click option'

Acontainer

Bservices

Clogger

Dinject

Attempts:

3 left

💡 Hint

Common Mistakes

Using different property names in middleware and route causing undefined errors.

Forgetting to call next() in middleware.

Both middleware and route handler use 'req.container' to access injected services consistently.

5fill in blank

hard

Fill all three blanks to define a service, inject it via middleware, and use it in a route.

Express

const greeterService = {
  greet: () => '[1]'
};

function injectServices(req, res, next) {
  req.[2] = { greeter: greeterService };
  next();
}

app.get('/hello', (req, res) => {
  res.send(req.[3].greeter.greet());
});

Drag options to blanks, or click blank then click option'

AHello, friend!

Bcontainer

Dservices

Attempts:

3 left

💡 Hint

Common Mistakes

Using different property names for injection and access.

Returning the wrong greeting string.

The service returns a greeting string. Middleware injects it into 'req.container'. The route reads from 'req.container' to call the greet method.

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