ModuleRef is a reference to the current module's DI container. Inject it to resolve providers imperatively at runtime — useful when you need a provider conditionally or need to retrieve a transient/request-scoped provider dynamically. Use moduleRef.get() for singletons and moduleRef.resolve() for scoped providers.

Using ModuleRef to resolve providers dynamically

Common use cases:

1
Strategy pattern — dynamically choose which provider to use at runtime.
2
Lazy initialization — resolve a heavy provider only when first needed.
3
Factory services — create instances of transient providers on demand.
4
moduleRef.get() is synchronous and only works for singleton providers.
5
moduleRef.resolve() is async and creates a new DI sub-context for scoped providers.

Difficulty: 5/10

Topics: dynamic provider resolution, runtime dependency injection, module ref usage

Scenario Questions

0-2 years experience

1
You need to get an instance of a service inside a NestJS guard, but you can't inject it via the constructor. How would you use ModuleRef to retrieve it?
2
If you call moduleRef.get(MyService, { strict: false }) and the provider isn't registered, what will happen at runtime?
3
What would be the result of requesting a request‑scoped provider using ModuleRef from within a singleton?

2-5 years experience

1
During a feature rollout you want to lazily load a heavy third‑party client only when a specific endpoint is hit. Walk me through how you'd use ModuleRef to achieve that and the trade‑offs you consider.
2
Your app started throwing 'Nest can't resolve dependencies' after moving a provider into a dynamic module. How could ModuleRef help you debug or fix the issue?
3
You have a plugin system where modules are registered at runtime. How would you use ModuleRef to instantiate a plugin's service and ensure its dependencies are satisfied?

5-8 years experience

1
At high traffic you notice that using ModuleRef.get inside a controller adds latency. What strategies would you employ to mitigate the performance impact while keeping dynamic resolution?
2
Design a mechanism for hot‑reloading feature modules without restarting the NestJS app. How would ModuleRef be involved, and what edge cases must you handle?
3
Explain how you would coordinate ModuleRef usage across multiple microservices that share a common library, ensuring consistent provider instances.

8+ years experience

1
Your organization is migrating a monolith to a modular NestJS architecture. How would you leverage ModuleRef to gradually refactor code, and what governance policies would you set to avoid runtime injection pitfalls?
2
When several teams add dynamic modules that rely on the same token, what architectural guidelines would you establish around ModuleRef usage to prevent token collisions and maintain testability?
3
Consider a long‑running background job system that resolves providers at runtime based on a job type stored in a database. How would you design this using ModuleRef to be resilient to schema changes and versioned modules?

Follow-up Questions

❓What are the risks of using ModuleRef inside a singleton service?
❓How does the 'strict' flag change the behavior of ModuleRef.get?
❓In what ways does ModuleRef improve or hurt testability compared to @Inject?