Why Constructor injection in NestJS? - Purpose & Use Cases

The Big Idea

Discover how constructor injection frees you from messy manual setup and makes your NestJS code shine!

The Scenario

Imagine building a NestJS service that needs to use a database and a logger. You have to create and manage these dependencies yourself inside the service.

The Problem

Manually creating and managing dependencies inside your service leads to messy code, tight coupling, and makes testing very hard. You must remember to create and pass every dependency everywhere.

The Solution

Constructor injection lets NestJS automatically provide the needed dependencies when creating your service. You just declare what you need in the constructor, and NestJS handles the rest.

Before vs After

✗ Before

class UserService {
  constructor() {
    this.db = new Database();
    this.logger = new Logger();
  }
}

✓ After

class UserService {
  constructor(private db: Database, private logger: Logger) {}
}

What It Enables

This makes your code cleaner, easier to test, and lets NestJS manage dependencies for you automatically.

Real Life Example

When building a user service, constructor injection lets you swap the database or logger easily without changing the service code, perfect for testing or changing implementations.

Key Takeaways

Manual dependency management is error-prone and messy.

Constructor injection lets NestJS provide dependencies automatically.

This leads to cleaner, more maintainable, and testable code.