Modules in NestJS

Welcome back! In the previous units, we’ve touched on modules as part of the broader NestJS architecture. Now, it's time to explore modules in greater depth. Understanding modules is key to building scalable, maintainable applications that adhere to best practices like the SOLID principles.

In NestJS, modules are classes marked with the @Module decorator. Each NestJS application must have at least one module—the root module, which serves as the entry point for the application. Modules help in organizing your application by grouping related components like controllers, providers, and services into a cohesive block.

import { Module } from '@nestjs/common';

@Module({
  imports: [],
  controllers: [],
  providers: [],
})
export class AppModule {}

• @Module Decorator: This decorator defines a module, specifying what controllers, providers, and other modules it contains.
• Root Module: Every NestJS application starts with a root module (the AppModule), which is the main entry point of the application.

To maintain a well-organized codebase, it’s common practice to break down an application into multiple feature modules. This approach allows you to encapsulate related logic and components, making the code more modular and easier to manage.

Let's consider an example where we combine our CorgiController and CorgiService into a dedicated CorgiModule.

import { Module } from '@nestjs/common';
import { CorgiController } from './corgi.controller';
import { CorgiService } from './corgi.service';

@Module({
  controllers: [CorgiController],
  providers: [CorgiService],
})
export class CorgiModule {}

• Feature Module: Here, CorgiModule encapsulates everything related to Corgis, keeping the application organized and adhering to the Single Responsibility Principle.
• Cohesion: This structure enhances cohesion by grouping related functionality together, making the codebase easier to navigate and extend.

In earlier units, we introduced the AppModule, the root module of your NestJS application. The AppModule is the entry point and is responsible for bootstrapping the application. It is where you import other modules, including feature modules like the CorgiModule, to integrate different parts of your application.

The AppModule often serves as a hub, connecting various modules and making sure the application components work together seamlessly.