Can a feature module re-export an imported module in NestJS? When is this useful?
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:
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.