Can a feature module re-export an imported module in NestJS? When is this useful?

Q: Can a feature module re-export an imported module in NestJS? When is this useful?

// CoreModule bundles several shared modules and re-exports all @Module({ imports: [HttpModule, ConfigModule, LoggerModule], exports: [HttpModule, ConfigModule, LoggerModule], }) export class CoreModule {} // Any module that imports CoreModule automatically gets // HttpService, ConfigService, and LoggerService available @Module({ imports: [CoreModule], providers: [UsersService], }) export class UsersModule {} Infrastructure bundles — group HttpModule, ConfigModule, LoggerModule into one CoreModule import. Layered APIs — a parent module exposes a sub-module's providers without exposing the sub-module's internals. Library modules — a library re-exports third-party modules it wraps so consumers don't need direct dependencies. Re-exporting a module is equivalent to exporting all of its exported providers at once.

Difficulty: 5/10

module re-export, dependency injection, module organization

Yes — a module can re-export any module it imports, making that module's exports available to any consumer of the re-exporting module. This is the standard pattern for building layered shared infrastructure that avoids every feature module importing the same set of utility modules individually.

Re-exporting an imported module

When re-exporting is useful:

1
Infrastructure bundles — group HttpModule, ConfigModule, LoggerModule into one CoreModule import.
2
Layered APIs — a parent module exposes a sub-module's providers without exposing the sub-module's internals.
3
Library modules — a library re-exports third-party modules it wraps so consumers don't need direct dependencies.
4
Re-exporting a module is equivalent to exporting all of its exported providers at once.

Scenario Questions

0-2 years experience

2-5 years experience

Follow-up Questions