Points d’extension avec l’API de référence des modules
Résolvez impérativement les dépendances associées à un périmètre via ModuleRef pour alimenter des extensions tierces.
Points d’extension avec l’API de référence des modules est une leçon NestJS Enterprise Backend APIs gratuite sur CoddyKit. Ceci est la leçon 4 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage NestJS Enterprise Backend APIs, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours NestJS Enterprise Backend APIs comprend 4 leçons au total.
Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.
Why ModuleRef Exists
NestJS resolves dependencies declaratively: you list providers in a constructor and the container wires them. But a plugin host can't know its extensions at compile time. You need to ask the container for a provider imperatively, at runtime.
ModuleRef is the DI container's public handle. It lets you:
- Retrieve an existing singleton by token (
get). - Resolve a scoped (REQUEST / TRANSIENT) instance on demand (
resolve). - Instantiate a class that was never registered as a provider (
create).
This is the foundation for plugin architectures and hexagonal extension points where adapters are chosen dynamically.
Injecting ModuleRef
ModuleRef is itself an injectable. Add it to any provider's constructor and Nest hands you the reference to the module instance that owns this provider.
Note that you cannot call get() in the constructor body if the dependency isn't ready yet — prefer onModuleInit for eager lookups so the whole module tree is constructed first.
import { Injectable, OnModuleInit } from '@nestjs/common';
import { ModuleRef } from '@nestjs/core';
import { AuditService } from './audit.service';
@Injectable()
export class PluginHost implements OnModuleInit {
private audit: AuditService;
constructor(private readonly moduleRef: ModuleRef) {}
onModuleInit() {
// Safe here: all providers are already instantiated.
this.audit = this.moduleRef.get(AuditService);
}
}get() — Retrieving Singletons
moduleRef.get(token) returns an already-instantiated singleton-scoped provider. It is synchronous and returns the same instance every call.
- By default the lookup is scoped to the current module.
- Pass
{ strict: false }to search the entire application (useful when the provider lives in another module that wasn't imported here).
get() throws if the token is request- or transient-scoped — those require resolve().
// Same module — strict (default)
const local = this.moduleRef.get(LocalCache);
// Anywhere in the app graph — non-strict
const global = this.moduleRef.get(ConfigService, { strict: false });
// String / Symbol tokens work too
const driver = this.moduleRef.get<StorageDriver>('STORAGE_DRIVER', {
strict: false,
});resolve() — Scoped Instances
Request- and transient-scoped providers do not have a single instance, so get() can't return one. Use the asynchronous resolve() instead.
Each call to resolve() returns a brand-new transient sub-tree by default. Two calls give two different instances — important when a plugin must not share mutable state.
import { Injectable } from '@nestjs/common';
import { ModuleRef } from '@nestjs/core';
import { TenantProcessor } from './tenant.processor'; // @Injectable({ scope: Scope.TRANSIENT })
@Injectable()
export class JobRunner {
constructor(private readonly moduleRef: ModuleRef) {}
async run() {
const a = await this.moduleRef.resolve(TenantProcessor);
const b = await this.moduleRef.resolve(TenantProcessor);
console.log(a === b); // false — distinct transient instances
}
}Sharing a Scoped Sub-Tree with contextId
Sometimes you want several resolve() calls to share the same request-scoped instances — for example all plugins handling one request should see the same RequestContext.
Pass a contextId to bind resolutions together. Generate one with ContextIdFactory.create() and reuse it.
import { ContextIdFactory, ModuleRef } from '@nestjs/core';
const contextId = ContextIdFactory.create();
const ctx = await this.moduleRef.resolve(RequestContext, contextId);
const svc = await this.moduleRef.resolve(ReportService, contextId);
// ctx and svc share the SAME request-scoped sub-tree
const other = await this.moduleRef.resolve(ReportService, contextId);
console.log(svc === other); // true — same contextId reuses the instanceRegistering the Request Payload
When you create your own contextId outside the normal HTTP pipeline, request-scoped providers that inject REQUEST have nothing to receive. You must register the payload manually with registerRequestByContextId.
This is the key trick for running request-scoped plugins inside cron jobs, queues, or WebSocket handlers where no Express request exists.
import { ContextIdFactory, ModuleRef, REQUEST } from '@nestjs/core';
const contextId = ContextIdFactory.create();
// Inject a synthetic 'request' for this context
this.moduleRef.registerRequestByContextId({ tenantId: 'acme' }, contextId);
// Now request-scoped providers resolve correctly off the queue
const handler = await this.moduleRef.resolve(TenantHandler, contextId);
await handler.process();create() — Instantiating Unregistered Classes
Plugins often ship classes the host never declared as providers. moduleRef.create(SomeClass) instantiates such a class while still injecting its constructor dependencies from the container.
- The result is not cached — every call builds a fresh instance.
- The class itself does not need an
@Injectable()registration, but its dependencies must be resolvable in the module graph.
This is how you load a plugin class by name and still give it access to core services.
import { Injectable } from '@nestjs/common';
import { ModuleRef } from '@nestjs/core';
// Shipped by a third party, never in any providers array
class SlackNotifier {
constructor(private readonly http: HttpClient) {}
notify(msg: string) { return this.http.post('/slack', { msg }); }
}
@Injectable()
export class ExtensionLoader {
constructor(private readonly moduleRef: ModuleRef) {}
async load() {
// http is injected from the container, SlackNotifier is not registered
const plugin = await this.moduleRef.create(SlackNotifier);
return plugin;
}
}A Token-Driven Plugin Registry
Combine a multi-provider token with ModuleRef to build an extension point. Plugins self-register under one injection token; the host resolves them and dispatches by capability.
The EXTENSIONS array is collected by Nest at boot; ModuleRef is reserved for lazy or scoped lookups the array can't express.
import { Inject, Injectable } from '@nestjs/common';
export const EXTENSIONS = Symbol('EXTENSIONS');
export interface Extension {
readonly name: string;
handle(event: unknown): Promise<void>;
}
@Injectable()
export class ExtensionDispatcher {
constructor(@Inject(EXTENSIONS) private readonly exts: Extension[]) {}
async dispatch(name: string, event: unknown) {
const ext = this.exts.find((e) => e.name === name);
if (!ext) throw new Error(`No extension: ${name}`);
await ext.handle(event);
}
}Hexagonal Adapters Chosen at Runtime
In hexagonal design the core depends on a port (interface) and stays ignorant of adapters. ModuleRef lets you pick the concrete adapter at runtime from configuration — the classic strategy-by-token pattern.
Use non-strict get() with a string token so the adapter can live in any imported module.
import { Injectable } from '@nestjs/common';
import { ModuleRef } from '@nestjs/core';
export interface PaymentPort {
charge(cents: number): Promise<string>;
}
@Injectable()
export class PaymentFacade {
constructor(private readonly moduleRef: ModuleRef) {}
private adapterToken(provider: string) {
return `PAYMENT_ADAPTER_${provider.toUpperCase()}`;
}
pick(provider: string): PaymentPort {
// e.g. PAYMENT_ADAPTER_STRIPE registered in StripeModule
return this.moduleRef.get<PaymentPort>(this.adapterToken(provider), {
strict: false,
});
}
}Modeling the Lifecycle in Plain TS
Strip away the framework and the contract is just: register adapters by key, then resolve one on demand. This standalone TypeScript program mirrors what ModuleRef.get does over a token registry — useful for unit-testing the dispatch logic in isolation.
interface PaymentPort {
charge(cents: number): string;
}
class StripeAdapter implements PaymentPort {
charge(cents: number): string {
return `stripe:charged ${cents}`;
}
}
class PaypalAdapter implements PaymentPort {
charge(cents: number): string {
return `paypal:charged ${cents}`;
}
}
class Registry {
private map = new Map<string, PaymentPort>();
register(key: string, port: PaymentPort): void {
this.map.set(key, port);
}
get(key: string): PaymentPort {
const p = this.map.get(key);
if (!p) throw new Error(`No adapter: ${key}`);
return p;
}
}
const registry = new Registry();
registry.register('stripe', new StripeAdapter());
registry.register('paypal', new PaypalAdapter());
const chosen = 'paypal';
console.log(registry.get(chosen).charge(1999));
console.log(registry.get('stripe').charge(500));Pitfalls & Best Practices
Use ModuleRef deliberately — it is an escape hatch, not a default.
- Don't call
get()in a constructor for providers that may not exist yet; useonModuleInit. - Never
get()a scoped provider — it throws; useresolve(). - Remember
resolve()andcreate()are async and uncached; awaiting in a hot path costs allocations. - Prefer constructor injection when the dependency is known statically — ModuleRef hides the graph from static analysis and tests.
- Tie request-scoped resolutions to one
contextIdand register the request payload off-pipeline.
Quick Check
You need to obtain an instance of a REQUEST-scoped provider from a queue consumer where no HTTP request exists, and all plugins for that job must share the same request-scoped state. Which approach is correct?
Recap
You learned to resolve dependencies imperatively for plugin and hexagonal extension points:
get(token, { strict })— synchronous singleton lookup, optionally across the whole app.resolve(token, contextId?)— async scoped resolution; a sharedcontextIdties instances into one sub-tree.registerRequestByContextId— injects a synthetic request so request-scoped providers work off-pipeline.create(Class)— instantiates an unregistered plugin class while still injecting its dependencies.
Reach for ModuleRef only when the dependency is dynamic; prefer plain constructor injection everywhere else.
Questions Fréquemment Posées
La leçon « Points d’extension avec l’API de référence des modules » est-elle gratuite ?
Oui — le texte complet de « Points d’extension avec l’API de référence des modules » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours NestJS Enterprise Backend APIs, passe à CoddyKit PRO. Le cours NestJS Enterprise Backend APIs comprend 4 leçons au total.
Qu'est-ce que j'apprendrai dans « Points d’extension avec l’API de référence des modules » ?
Résolvez impérativement les dépendances associées à un périmètre via ModuleRef pour alimenter des extensions tierces. Tu pratiques NestJS Enterprise Backend APIs avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.
Dois-je avoir de l'expérience pour commencer NestJS Enterprise Backend APIs ?
Aucune expérience préalable n'est requise. NestJS Enterprise Backend APIs sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 4 sur 4.
Combien de temps prend la leçon « Points d’extension avec l’API de référence des modules » ?
La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.
Peux-tu écrire et exécuter du code dans cette leçon NestJS Enterprise Backend APIs ?
Oui. Chaque leçon NestJS Enterprise Backend APIs inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.
Toutes les leçons de ce cours
- Ports et adaptateurs pour isoler le domaine
- Enregistrement dynamique des fournisseurs avec DiscoveryService
- Modules chargés à la demande et bascules de fonctionnalités
- Points d’extension avec l’API de référence des modules