What is a dynamic module in NestJS and how is it different from a static module?

Q: What is a dynamic module in NestJS and how is it different from a static module?

// Static module — same behaviour every time @Module({ providers: [MailService], exports: [MailService] }) export class MailModule {} // Dynamic module — caller controls behaviour via options @Module({}) export class MailModule { static forRoot(options: MailOptions): DynamicModule { return { module: MailModule, providers: [ { provide: MAIL_OPTIONS, useValue: options }, MailService, ], exports: [MailService], }; } } // Usage @Module({ imports: [MailModule.forRoot({ host: 'smtp.example.com', port: 587 })], }) export class AppModule {} Library modules that need to behave differently based on caller configuration. Modules that wrap third-party SDKs and need connection options at import time. Any module whose providers depend on runtime values not known at compile time. Standard examples: TypeOrmModule.forRoot(), JwtModule.register(), ConfigModule.forRoot().

What is a dynamic module in NestJS and how is it different from a static module? | Modules | NestJS Interview Questions | NextRound.in

What is a dynamic module in NestJS and how is it different from a static module?

What is a dynamic module in NestJS and how is it different from a static module?

Scenario Questions

Follow-up Questions