What is LazyModuleLoader in NestJS and how does it differ from standard DI?

Q: What is LazyModuleLoader in NestJS and how does it differ from standard DI?

@Injectable() export class ReportService { constructor(private lazyLoader: LazyModuleLoader) {} async generatePdf(data: any) { // PdfModule and all its providers are initialized only on first call const moduleRef = await this.lazyLoader.load( () => import('./pdf/pdf.module').then(m => m.PdfModule), ); const { PdfService } = await import('./pdf/pdf.service'); const pdfService = moduleRef.get(PdfService); return pdfService.generate(data); // subsequent calls reuse cached module } } Standard DI — all providers instantiated at app startup; module graph fully resolved before app accepts requests. LazyModuleLoader — module initialized on first access; reduces startup time and memory for rarely-used features. Lazy modules are cached after first load — subsequent calls use the same module instance. Controllers cannot be lazy-loaded — only service-level providers in the lazy module. Best for: report generation, image processing, export features, admin-only operations.

Difficulty: 5/10

lazy loading, dependency injection, module architecture

Standard DI resolves all providers at bootstrap time. LazyModuleLoader defers a module's initialization until its providers are first accessed at runtime. After the first load the module is cached. It is useful for heavy optional modules like PDF generation or image processing that are rarely invoked.

Lazy loading a module on demand

Differences from standard DI:

1
Standard DI — all providers instantiated at app startup; module graph fully resolved before app accepts requests.
2
LazyModuleLoader — module initialized on first access; reduces startup time and memory for rarely-used features.
3

What is LazyModuleLoader in NestJS and how does it differ from standard DI?

Difficulty: 5/10

lazy loading, dependency injection, module architecture

Standard DI resolves all providers at bootstrap time. LazyModuleLoader defers a module's initialization until its providers are first accessed at runtime. After the first load the module is cached. It is useful for heavy optional modules like PDF generation or image processing that are rarely invoked.

Lazy loading a module on demand

Differences from standard DI:

1
Standard DI — all providers instantiated at app startup; module graph fully resolved before app accepts requests.
2
LazyModuleLoader — module initialized on first access; reduces startup time and memory for rarely-used features.
3

What is LazyModuleLoader in NestJS and how does it differ from standard DI?

What is LazyModuleLoader in NestJS and how does it differ from standard DI?

Scenario Questions

Follow-up Questions