Module re-exporting in NestJS - Mini Project: Build & Apply

NestJS Module Re-exporting

📖 Scenario: You are building a NestJS application that has two feature modules: UsersModule and AuthModule. You want to create a SharedModule that re-exports these two modules so other parts of the app can import just the SharedModule to get access to both.

🎯 Goal: Build a SharedModule that imports and re-exports UsersModule and AuthModule so other modules can use their providers by importing only SharedModule.

📋 What You'll Learn

Create a UsersModule with a simple provider

Create an AuthModule with a simple provider

Create a SharedModule that imports and re-exports UsersModule and AuthModule

Use NestJS module syntax with @Module decorator and imports and exports arrays

💡 Why This Matters

🌍 Real World

In real NestJS apps, re-exporting modules via a SharedModule helps keep imports clean and organized. It lets you group related modules and share their providers easily.

💼 Career

Understanding module re-exporting is important for building scalable NestJS applications and working in teams where modular architecture is required.

1

Create UsersModule with a provider

Create a NestJS module called UsersModule that provides a class called UsersService. Use the @Module decorator with a providers array containing UsersService.

NestJS

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

// Your code here

Hint

Remember to export UsersService and include it in both providers and exports arrays so it can be used outside the module.

2

Create AuthModule with a provider

Create a NestJS module called AuthModule that provides a class called AuthService. Use the @Module decorator with a providers array containing AuthService and export AuthService as well.

NestJS

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

export class UsersService {}

@Module({
  providers: [UsersService],
  exports: [UsersService],
})
export class UsersModule {}

// Your code here

Hint

Follow the same pattern as UsersModule but for AuthService and AuthModule.

3

Create SharedModule importing UsersModule and AuthModule

Create a NestJS module called SharedModule that imports UsersModule and AuthModule. Use the @Module decorator with an imports array containing UsersModule and AuthModule.

NestJS

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

export class UsersService {}

@Module({
  providers: [UsersService],
  exports: [UsersService],
})
export class UsersModule {}

export class AuthService {}

@Module({
  providers: [AuthService],
  exports: [AuthService],
})
export class AuthModule {}

// Your code here

Hint

Use both imports and exports arrays in @Module to re-export the imported modules.

4

Use SharedModule in another module

Create a NestJS module called AppModule that imports only the SharedModule. Use the @Module decorator with an imports array containing SharedModule.

NestJS

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

export class UsersService {}

@Module({
  providers: [UsersService],
  exports: [UsersService],
})
export class UsersModule {}

export class AuthService {}

@Module({
  providers: [AuthService],
  exports: [AuthService],
})
export class AuthModule {}

@Module({
  imports: [UsersModule, AuthModule],
  exports: [UsersModule, AuthModule],
})
export class SharedModule {}

// Your code here

Hint

This shows how other modules can import SharedModule to get access to UsersModule and AuthModule providers.

Practice

1. What is the main purpose of module re-exporting in NestJS?

easy

A. To share modules through another module for better organization

B. To create multiple instances of the same module

C. To prevent modules from being imported anywhere

D. To automatically generate services inside a module

Solution

1. Step 1: Understand module re-exporting concept

   Module re-exporting allows one module to share its imported modules with other modules by re-exporting them.

2. Step 2: Identify the purpose in NestJS

   This helps keep the app organized and makes modules easier to maintain by avoiding repeated imports.

3. Final Answer:

   To share modules through another module for better organization -> Option A

4. Quick Check:

   Module re-exporting = sharing modules [OK]

Hint: Re-exporting means sharing modules via another module [OK]

Common Mistakes:

• Thinking re-exporting creates new module instances
• Believing it blocks module imports
• Confusing it with automatic service generation

2. Which syntax correctly re-exports a module named SharedModule inside another module's decorator?

easy

A. @Module({ exports: [SharedModule] })

B. @Module({ imports: [], exports: [SharedModule] })

C. @Module({ imports: [SharedModule] })

D. @Module({ imports: [SharedModule], exports: [SharedModule] })

Solution

1. Step 1: Recall NestJS module decorator structure

   To re-export a module, it must be both imported and exported in the module decorator.

2. Step 2: Check each option

   The syntax with both imports: [SharedModule] and exports: [SharedModule] is correct. Syntaxes missing either array are incorrect.

3. Final Answer:

   @Module({ imports: [SharedModule], exports: [SharedModule] }) -> Option D

4. Quick Check:

   Import and export to re-export [OK]

Hint: Re-export needs both imports and exports arrays [OK]

Common Mistakes:

• Only exporting without importing
• Only importing without exporting
• Leaving either array empty when re-exporting

3. Given these modules, what will be the output of console.log(appModuleImports) if AppModule imports CoreModule which re-exports SharedModule?

@Module({ imports: [SharedModule], exports: [SharedModule] })
export class CoreModule {}

@Module({ imports: [CoreModule] })
export class AppModule {}

Assuming appModuleImports is the list of modules available inside AppModule.

medium

A. [SharedModule]

B. [CoreModule, SharedModule]

C. [CoreModule]

D. []

Solution

1. Step 1: Understand re-export effect on imports

   CoreModule imports and exports SharedModule, so any module importing CoreModule also gets SharedModule.

2. Step 2: Analyze AppModule imports

   AppModule imports CoreModule, so it has access to both CoreModule and SharedModule.

3. Final Answer:

   [CoreModule, SharedModule] -> Option B

4. Quick Check:

   Re-exported modules appear in importing module imports [OK]

Hint: Re-exported modules appear as if directly imported [OK]

Common Mistakes:

• Assuming only CoreModule is available
• Thinking SharedModule is hidden
• Ignoring exports array effect

4. Identify the error in this module re-exporting code:

@Module({
  imports: [SharedModule],
  exports: []
})
export class CoreModule {}

medium

A. SharedModule is imported but not exported, so it is not re-exported

B. SharedModule should not be in imports when re-exporting

C. exports array cannot be empty in any module

D. CoreModule must import AppModule to re-export SharedModule

Solution

1. Step 1: Check imports and exports arrays

   SharedModule is imported but not exported, so CoreModule does not re-export it.

2. Step 2: Understand re-export requirement

   To re-export a module, it must be listed in both imports and exports arrays.

3. Final Answer:

   SharedModule is imported but not exported, so it is not re-exported -> Option A

4. Quick Check:

   Re-export needs both imports and exports [OK]

Hint: Exports must include imported modules to re-export [OK]

Common Mistakes:

• Leaving exports empty when re-exporting
• Confusing imports-only as re-export
• Thinking exports array is optional

5. You have three modules: SharedModule, CoreModule, and FeatureModule. CoreModule imports and re-exports SharedModule. FeatureModule imports CoreModule. How can you modify FeatureModule to also re-export SharedModule without importing it directly?

hard

A. Add imports: [SharedModule] in FeatureModule

B. Add exports: [SharedModule] in FeatureModule

C. Add exports: [CoreModule] in @Module decorator of FeatureModule

D. Add providers: [SharedModule] in FeatureModule

Solution

1. Step 1: Understand re-export chaining

   FeatureModule imports CoreModule, which re-exports SharedModule, so FeatureModule has access to SharedModule.

2. Step 2: Re-export SharedModule via CoreModule

   To re-export SharedModule from FeatureModule without importing it directly, FeatureModule must export CoreModule.

3. Final Answer:

   Add exports: [CoreModule] in @Module decorator of FeatureModule -> Option C

4. Quick Check:

   Export imported module to re-export its exports [OK]

Hint: Export imported module to re-export its exports [OK]

Common Mistakes:

• Trying to export SharedModule without importing it
• Adding SharedModule to providers array
• Importing SharedModule directly instead of re-exporting