How do you implement forRootAsync() in a dynamic module so that options can be loaded asynchronously from ConfigService?

Q: How do you implement forRootAsync() in a dynamic module so that options can be loaded asynchronously from ConfigService?

@Module({}) export class DatabaseModule { static forRootAsync(options: DatabaseAsyncOptions): DynamicModule { return { module: DatabaseModule, imports: options.imports || [], providers: [ { provide: DB_OPTIONS, useFactory: options.useFactory, inject: options.inject || [], }, DatabaseService, ], exports: [DatabaseService], }; } } // Usage — options resolved from ConfigService @Module({ imports: [ DatabaseModule.forRootAsync({ imports: [ConfigModule], useFactory: (config: ConfigService) => ({ url: config.get('DATABASE_URL'), ssl: config.get('DATABASE_SSL') === 'true', }), inject: [ConfigService], }), ], }) export class AppModule {} The options object mirrors the NestJS provider API — useFactory, useClass, useExisting are all valid. Pass imports and inject from the caller's options into the dynamic module's returned object. The factory receives resolved provider instances as arguments in the order listed in inject. This is the exact pattern used by @nestjs/config, @nestjs/typeorm, and @nestjs/jwt.

Difficulty: 6/10

Dynamic Modules, Async Providers, ConfigService Integration

forRootAsync() accepts an options object that mirrors the custom provider API — supporting useFactory, useClass, or useExisting. The caller provides a factory function that receives injected providers as arguments, and the dynamic module wires them into the provider token that the module's services depend on.

forRootAsync() implementation and usage

Key implementation points:

1
The options object mirrors the NestJS provider API — useFactory, useClass, useExisting are all valid.
2
Pass imports and inject from the caller's options into the dynamic module's returned object.

How do you implement forRootAsync() in a dynamic module so that options can be loaded asynchronously from ConfigService?

Difficulty: 6/10

Dynamic Modules, Async Providers, ConfigService Integration

forRootAsync() accepts an options object that mirrors the custom provider API — supporting useFactory, useClass, or useExisting. The caller provides a factory function that receives injected providers as arguments, and the dynamic module wires them into the provider token that the module's services depend on.

forRootAsync() implementation and usage

Key implementation points:

1
The options object mirrors the NestJS provider API — useFactory, useClass, useExisting are all valid.
2
Pass imports and inject from the caller's options into the dynamic module's returned object.

How do you implement forRootAsync() in a dynamic module so that options can be loaded asynchronously from ConfigService?

How do you implement forRootAsync() in a dynamic module so that options can be loaded asynchronously from ConfigService?

Scenario Questions

Follow-up Questions