Module re-exporting in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to export the imported module in NestJS.

NestJS

import { Module } from '@nestjs/common';
import { UsersModule } from './users.module';

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

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

AUsersModule

BSharedModule

CAppModule

DCommonModule

Attempts:

3 left

💡 Hint

Common Mistakes

Exporting the current module instead of the imported one.

Forgetting to export the module after importing.

You export UsersModule so other modules importing SharedModule can use it.

2fill in blank

medium

Complete the code to re-export multiple modules in NestJS.

NestJS

import { Module } from '@nestjs/common';
import { UsersModule } from './users.module';
import { AuthModule } from './auth.module';

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

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

AUsersModule

B[UsersModule, AuthModule]

CAuthModule

D[]

Attempts:

3 left

💡 Hint

Common Mistakes

Exporting only one module when multiple are imported.

Not using an array for multiple exports.

To re-export multiple modules, list them inside an array in the exports property.

3fill in blank

hard

Fix the error in the code to properly re-export the imported module.

NestJS

import { Module } from '@nestjs/common';
import { ProductsModule } from './products.module';

@Module({
  imports: [ProductsModule],
  exports: [1],
})
export class InventoryModule {}

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

AProductsModule

BInventoryModule

C[]

D[ProductsModule]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a single module without array brackets in exports.

Confusing imports and exports syntax.

The exports property expects an array, so wrap ProductsModule in square brackets.

4fill in blank

hard

Fill both blanks to create a module that imports and re-exports two modules.

NestJS

import { Module } from '@nestjs/common';
import { OrdersModule } from './orders.module';
import { PaymentsModule } from './payments.module';

@Module({
  imports: [[1], [2]],
  exports: [OrdersModule, PaymentsModule],
})
export class TransactionsModule {}

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

AOrdersModule

BPaymentsModule

CUsersModule

DAuthModule

Attempts:

3 left

💡 Hint

Common Mistakes

Importing modules not listed in exports.

Swapping module names.

You import both OrdersModule and PaymentsModule so you can re-export them.

5fill in blank

hard

Fill all three blanks to create a module that imports, re-exports, and uses a service from another module.

NestJS

import { Module } from '@nestjs/common';
import { NotificationsModule } from './notifications.module';
import { EmailService } from './email.service';

@Module({
  imports: [[1]],
  exports: [[2]],
  providers: [[3]],
})
export class MessagingModule {}

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

ANotificationsModule

CEmailService

DAuthService

Attempts:

3 left

💡 Hint

Common Mistakes

Putting services in imports or exports instead of providers.

Not re-exporting the imported module.

You import and export NotificationsModule to re-export it, and provide EmailService for use inside this module.

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