How can a dynamic module expose a forFeature() method that works alongside a forRoot() registration in NestJS?

Q: How can a dynamic module expose a forFeature() method that works alongside a forRoot() registration in NestJS?

@Module({}) export class DatabaseModule { // Called once in AppModule — registers the connection globally static forRoot(options: DbOptions): DynamicModule { return { module: DatabaseModule, global: true, providers: [ { provide: DB_OPTIONS, useValue: options }, ConnectionService, ], exports: [ConnectionService], }; } // Called per feature module — registers entity-specific repositories static forFeature(entities: EntityClass[]): DynamicModule { const repoProviders = entities.map(entity => ({ provide: getRepositoryToken(entity), useFactory: (conn: ConnectionService) => conn.getRepository(entity), inject: [ConnectionService], // relies on forRoot() having registered this })); return { module: DatabaseModule, providers: repoProviders, exports: repoProviders, }; } } forRoot — registers infrastructure once globally: connections, global config, shared clients. forFeature — registers per-module resources: entity repositories, feature-scoped services. forFeature providers can inject forRoot providers because global providers are available app-wide. This pattern is used by TypeOrmModule, MongooseModule, and SequelizeModule in the NestJS ecosystem.

Difficulty: 6/10

Dynamic modules, forRoot/forFeature pattern, module registration

forRoot() registers global configuration once. forFeature() registers feature-specific providers that depend on the global config — similar to how TypeORM works with entities. forFeature() relies on providers from forRoot() being already registered globally, so it can inject them via the DI container.

forRoot() and forFeature() working together

forRoot vs forFeature responsibilities:

1
forRoot — registers infrastructure once globally: connections, global config, shared clients.
2
forFeature — registers per-module resources: entity repositories, feature-scoped services.
3
forFeature providers can inject forRoot providers because global providers are available app-wide.
4
This pattern is used by TypeOrmModule, MongooseModule, and SequelizeModule in the NestJS ecosystem.

Scenario Questions

0-2 years experience

1You need to add a new repository to an existing NestJS module that already uses forRoot(). How would you expose it using a forFeature() method?
2If you import a feature module that calls forFeature() twice with different providers, what will the injected service resolve to?
3What do you need to import in a feature module to get access to a service that was registered via the core module's forRoot()?

Follow-up Questions

What would happen if you forgot to export the providers from the forFeature() call?
How does NestJS determine the scope of a provider registered via forFeature() versus forRoot()?
Can you describe a situation where two feature modules might conflict because of shared provider tokens?