When should you export a module vs export individual providers from a module in NestJS?

Q: When should you export a module vs export individual providers from a module in NestJS?

// Fine-grained — only UsersService is public, helper stays private @Module({ providers: [UsersService, UsersInternalHelper], exports: [UsersService], }) export class UsersModule {} // Re-exporting a module — consumers get everything TypeOrmModule exports @Module({ imports: [TypeOrmModule.forFeature([User])], exports: [TypeOrmModule], // re-export the whole module }) export class UsersPersistenceModule {} Export individual providers when you want a clean, minimal public API and need to hide implementation details. Re-export a whole module when building infrastructure bundles or wrapper modules. Re-exporting exposes everything the re-exported module itself exports — no more, no less. Prefer individual exports for feature modules; prefer module re-exports for infrastructure aggregators.

Difficulty: 5/10

module exports, provider scope, dependency injection

Export individual providers for fine-grained control — internal helpers stay private. Re-export a whole module when you want to pass an entire module's public API through to consumers, which is useful for infrastructure bundles. Re-exporting a module is equivalent to exporting all of its exported providers at once.

Individual provider export vs module re-export

Decision guide:

1
Export individual providers when you want a clean, minimal public API and need to hide implementation details.
2
Re-export a whole module when building infrastructure bundles or wrapper modules.
3
Re-exporting exposes everything the re-exported module itself exports — no more, no less.
4
Prefer individual exports for feature modules; prefer module re-exports for infrastructure aggregators.

Scenario Questions

0-2 years experience

2-5 years experience

Follow-up Questions