Questions
11 of 11
1What is a provider in NestJS?
2What are the different forms of custom provider syntax in NestJS?
3How does NestJS handle async providers and what problem do they solve?
4What are provider scopes in NestJS and when would you change the default?
5How do you resolve a circular dependency between two providers in NestJS?
6Walk through all four custom provider types: useClass, useValue, useFactory, useExisting.
7How do you create a multi-provider pattern in NestJS to inject multiple implementations for the same token?
8How does an async provider work in NestJS and what guarantees does it give?
9What is the shorthand provider syntax in NestJS and what does it expand to?
10What is the difference between useExisting and useClass when aliasing a provider in NestJS?
11How do you make a provider accessible across the entire module graph using ModuleRef.get() with strict: false?
NestJSNestJS
Basics
Modules
Decorators
Controllers
Dependency Injection
Providers
Architecture
Request Lifecycle
Middleware
Guards
Interceptors
Pipes
Filters
Exception Handling
API Design
GraphQL
Database and ORM
Microservices
Authentication and Authorization
11 / 11

How do you make a provider accessible across the entire module graph using ModuleRef.get() with strict: false?

By default, moduleRef.get(token) only searches the current module's provider registry. Passing { strict: false } makes it search the entire global module graph. This should be used sparingly as it breaks module encapsulation and makes dependencies invisible in the module metadata.

Using strict: false with ModuleRef
When to use and when to avoid:
  1. 1

    Use strict: false only when the provider cannot be imported through the normal module graph.

  2. 2

    Prefer explicit module imports and exports over strict: false — they keep dependencies traceable.

  3. 3

    strict: false is useful in dynamic plugin systems or framework-level utilities.

  4. 4

    strict: false only works for singleton providers — scoped providers require moduleRef.resolve().