How does NestJS handle module initialization order and can you control it?

Q: How does NestJS handle module initialization order and can you control it?

// AppModule imports DatabaseModule and UsersModule // UsersModule imports DatabaseModule // Initialization order: // 1. DatabaseModule (deepest dependency first) // 2. UsersModule (its dependency DatabaseModule is ready) // 3. AppModule (all dependencies ready) // Use OnModuleInit for logic that needs all providers ready @Module({}) export class DatabaseModule implements OnModuleInit { constructor(private db: DatabaseService) {} async onModuleInit() { await this.db.connect(); // runs after all providers are instantiated console.log('Database connected'); } } NestJS initializes modules depth-first — deepest dependencies initialize first. Imported modules are always ready before the module that imports them. You cannot manually set initialization order — structure your imports to express the correct dependency direction. Use OnModuleInit for post-initialization logic — it fires after all providers in the module are instantiated. Use OnApplicationBootstrap for logic that must run after every module in the app is initialized.

Difficulty: 6/10

module lifecycle, dependency injection, initialization order

NestJS builds the module graph depth-first starting from the root module. Imported modules are always initialized before the module that imports them — dependencies are ready before their consumers. You cannot manually control the order but can rely on lifecycle hooks like OnModuleInit to run logic after all providers are instantiated.

Initialization order and lifecycle hooks

Initialization order rules:

1
NestJS initializes modules depth-first — deepest dependencies initialize first.
2
Imported modules are always ready before the module that imports them.
3
You cannot manually set initialization order — structure your imports to express the correct dependency direction.
4
Use OnModuleInit for post-initialization logic — it fires after all providers in the module are instantiated.
5
Use OnApplicationBootstrap for logic that must run after every module in the app is initialized.

Scenario Questions

0-2 years experience

2-5 years experience

Follow-up Questions