NestJS patterns -- modules, DI, exception filters, validation pipes, guards, interceptors, testing, config
98
89%
Does it follow best practices?
Impact
100%
1.36xAverage score across 12 eval scenarios
Passed
No known issues
A logistics company needs a NestJS API for tracking shipments. Build the initial project scaffold following NestJS best practices.
Requirements:
shipments feature module with POST /shipments (create), GET /shipments (list all), and GET /shipments/:id (get one) endpointstrackingNumber (non-empty string), origin (string), destination (string), weightKg (positive number)Follow NestJS best practices for project structure, error handling, validation, and response formatting.
Produce TypeScript source files in logistics-api/src/:
main.ts -- bootstrap file with all global configurationapp.module.ts -- root moduleshipments/shipments.module.ts -- feature moduleshipments/shipments.controller.ts -- controllershipments/shipments.service.ts -- stub serviceshipments/dto/create-shipment.dto.ts -- validated DTOcommon/filters/all-exceptions.filter.ts -- exception filtercommon/interceptors/logging.interceptor.ts -- logging interceptorDo not run npm install or start the server.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
nestjs-best-practices
verifiers