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.
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().