Dynamic modules su ne modules da za su iya a saita lokacin da aka shigo da su — maimakon static @Module({...}), suna bayarwa da static methods (jiya forRoot da ) waɗanda suke mayar da module da aka saitawa tare da arguments da ka yi amfani. Wannan shine yadda modules da za su iya jujjuyawa da sake amfani (config, database, JWT) suke karɓar options.
forFeatureA static module is fixed — but reusable modules (DatabaseModule, ConfigModule,
JwtModule) need to be CONFIGURED per app (connection URL, secret, options).
Dynamic modules let a module accept configuration at import time.
@Module({
imports: [
ConfigModule.forRoot({ isGlobal: true }), // ← forRoot with options
TypeOrmModule.forRoot({ type: "postgres", url: ... }), // ← configured at import
JwtModule.register({ secret: process.env.SECRET }), // ← register variant
TypeOrmModule.forFeature([User, Post]), // ← forFeature for specifics
],
})
export class AppModule {}
Dakin .forRoot()/.register()/.forFeature() da ka gani lokacin da ka shigo da modules shine hanyoyin dynamic-module methods waɗanda suke karɓar configuration.
forRoot() → configure the module ONCE, globally (the connection, the secret, core setup)
called in the root/app module a single time
forFeature() → register feature-specific pieces in each feature module that needs them
(e.g. TypeOrmModule.forFeature([User]) registers entities per module)
Al'ada: forRoot don jita-jita/lokaci gida configuration; forFeature don kowane feature registration da ka kira a cikin modules da yawa.
@Module({})
export class StorageModule {
static forRoot(options: StorageOptions): DynamicModule {
return { // returns a configured module
module: StorageModule,
providers: [
{ provide: "STORAGE_OPTIONS", useValue: options }, // inject the passed options
StorageService,
],
exports: [StorageService],
global: true, // optionally make it global
};
}
}
// usage: StorageModule.forRoot({ bucket: "my-bucket", region: "us-east-1" })
Static method yana mayarwa da DynamicModule object (module + providers + exports), da sanye wa passed options zuwa providers na module (sau da yawa ta hanyar injection token).
// configure using OTHER injected dependencies (e.g. ConfigService) — async/factory
StorageModule.forRootAsync({
useFactory: (config: ConfigService) => ({ bucket: config.get("BUCKET") }),
inject: [ConfigService],
});
forRootAsync variant yana bada izini configuration don dogara da sauran providers (kamar ConfigService) — aiki mai mahimmanci lokacin da options suka zo daga validated configuration.
Dynamic modules da tsarin forRoot/forFeature su ne mahimman NestJS concept don gina modules da za su iya jujjuyawa da sake amfani — da fahimtar su yana da daraja don amfani da ecosystem da kuma don gina modules da aka raba.
Kusan kowane major NestJS module (ConfigModule, TypeOrmModule, JwtModule, BullModule, CacheModule) shine dynamic module da aka saitawa ta hanyar .forRoot()/.register()/.forFeature(), don haka ganin abin da waɗannan kiran (bayarwa configuration zuwa module a lokacin shigo, maimakon static import) yana share daidai abin da duka ecosystem yake wireyi.
forRoot vs forFeature al'ada (forRoot don lokaci gida global setup kamar database connection ko sirri; forFeature don per-feature registration kamar jigiduwar entities a kowane module) shine tsari da ka hafu a kowa.
Gakin masu arziki, sanin yadda za ka gina ninka dynamic modules (mayarwa da DynamicModule tare da providers da aka saitawa daga passed options, sau da yawa ta hanyar injection tokens, tare da async variants don config-dependent setup) shine abin da ya bada izini ka gina modules da za su iya jujjuyawa da sake amfani — shared infrastructure (storage, external API clients, custom config) da sauran sassan app ko sauran projects suke shigo tare da ninka settings.
Wannan shine babbaka mafi ci gaba, amma shine abin da ke mahimmanci ga fahimtar NestJS's modular architecture zafin kula da gina professional, reusable module libraries, sa haka shi ne mahimman iya aiki don gina manyan, aiki-yaki-aiki NestJS systems.