NestJS DI Tokens and Module Binding Volume 07 - Advanced Application Architecture | Phase 24
Interfaces disappear at runtime TypeScript interfaces are compile-time only, so NestJS cannot inject TaskRepository directly. The runtime container needs a token. Current NestJS documentation explicitly supports strings, symbols, enums, classes, and abstract classes as provider tokens. TaskFlow chooses a Symbol to avoid accidental collisions.
Token and provider export const TASK_REPOSITORY = Symbol("TASK_REPOSITORY")
@Module({
providers: [
TasksService,
{
provide: TASK_REPOSITORY,
useClass: PrismaTaskRepository,
},
],
})
export class TasksModule {}Inject the contract constructor( @Inject(TASK_REPOSITORY) private readonly tasks: TaskRepository, ) {}
TasksService DI token PrismaTaskRepository TaskRepository contract TASK_REPOSITORY implements contract
PrismaService generated client + adapter
Why useClass matters The service depends on the token and interface shape, while the module decides which concrete implementation satisfies that dependency. Tests can supply a fake with useValue without
changing production code.
Authentication answers who the request represents. Treating decoded or client-supplied identity as trusted is a security boundary failure.
Restate the goal of “NestJS DI Tokens and Module Binding” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: credentials/session → token → verification → trusted identity → protected operation. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: One TaskFlow aggregate/use case refactored behind a purposeful repository interface with real database integration tests.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const token = readBearerToken(request);
const claims = await verifier.verify(token);
request.user = {
id: claims.sub,
email: claims.email,
};Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Inspect whether a token exists, whether it is expired, which issuer/audience signed it, and what the API verifier expects.
Trust only verified server claims; never repair identity by accepting a client-sent user id.
Without copying the final source, create a second small scenario that applies “NestJS DI Tokens and Module Binding” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Move Prisma-specific selection/query details into the implementation.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Mocks proving an imaginary database behavior
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.