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

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

@Injectable() export class FactoryService { constructor(private moduleRef: ModuleRef) {} getLocalService() { // strict: true (default) — only searches current module return this.moduleRef.get(LocalService); } getGlobalService() { // strict: false — searches entire application container return this.moduleRef.get(SomeOtherModuleService, { strict: false }); } } Use strict: false only when the provider cannot be imported through the normal module graph. Prefer explicit module imports and exports over strict: false — they keep dependencies traceable. strict: false is useful in dynamic plugin systems or framework-level utilities. strict: false only works for singleton providers — scoped providers require moduleRef.resolve().

Difficulty: 5/10

ModuleRef, Provider scope, Dependency injection

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
Use strict: false only when the provider cannot be imported through the normal module graph.
2
Prefer explicit module imports and exports over strict: false — they keep dependencies traceable.
3
strict: false is useful in dynamic plugin systems or framework-level utilities.
4
strict: false only works for singleton providers — scoped providers require moduleRef.resolve().

Scenario Questions

0-2 years experience

2-5 years experience

1While adding a feature module that is loaded lazily, the ConfigService isn’t injected automatically. Explain how you would fix this with ModuleRef.get and why strict:false is required.

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.

Scenario Questions

Follow-up Questions