Why Shared modules in NestJS? - Purpose & Use Cases

The Big Idea

Discover how shared modules can save you hours of frustrating code duplication!

The Scenario

Imagine building a NestJS app where you copy the same service code into multiple modules to use it everywhere.

The Problem

Copying code leads to mistakes, harder updates, and confusion about which version is current. It slows development and causes bugs.

The Solution

Shared modules let you write code once and share it cleanly across your app, keeping things organized and easy to maintain.

Before vs After

✗ Before

import { UserService } from './user.service';
import { Module } from '@nestjs/common';
@Module({ providers: [UserService], exports: [UserService] })
export class UserModule {}

// Then copy UserService to another module manually

✓ After

import { SharedModule } from './shared.module';
import { Module } from '@nestjs/common';
@Module({ imports: [SharedModule] })
export class OrderModule {}

What It Enables

It enables clean, reusable code that scales well as your app grows.

Real Life Example

When multiple parts of your app need to access the same database service, a shared module provides it once for all.

Key Takeaways

Copying code causes bugs and slows updates.

Shared modules let you write code once and reuse it everywhere.

This keeps your app clean, organized, and easy to grow.