How gitdagray/nestjs-course works
Project Type and Purpose
• This repository is a multi-chapter, hands-on NestJS tutorial. Each top-level folder (lesson01–lesson06) is a standalone NestJS REST API illustrating progressively advanced concepts: from controllers and providers, through DTO validation and error handling, to Prisma-backed database access and cross-cutting concerns (CORS, rate limiting, logging, exception filters).
File Structure
• Each lesson is structured as a standard NestJS application:
• nest-cli.json, tsconfig.json/tsconfig.build.json, package.json, ESLint/Prettier configs
• src/ containing main.ts (application entry), app.module.ts (root module), controllers, services, and any feature modules (users, employees, database, my-logger)
• test/ and src/**/*.spec.ts for e2e and unit tests
• Lessons 5 and 6 add:
• prisma/ folder with schema.prisma and migration scripts
• database module for PrismaClient injections
• cross-cutting filters and services (all-exceptions.filter.ts, my-logger)
• README sets the educational context and links each lesson.
README for Additional Insights
• Node.js + TypeScript + NestJS
• Prisma ORM + Neon Serverless Postgres
• Class-Validator for DTO validation
• Middleware: CORS, rate limiting, exception filters, custom logger
a. Main Components
• Client (e.g., browser, Postman, front-end)
• NestJS Application
– Entry Point (main.ts)
– AppModule (root DI container)
– Feature Modules (UsersModule, EmployeesModule, DatabaseModule, MyLoggerModule)
– Controllers (handling HTTP routes)
– Services (business logic)
– Pipes/Filters (validation pipe, exception filter)
• Prisma Client (injected via DatabaseModule)
• PostgreSQL Database (Neon serverless)
• External Cross-cutting Services (rate limiter, CORS middleware, custom logger)
b. Relationships & Interactions
1. HTTP request → NestJS middleware (CORS, rate limiting)
2. Validation Pipe transforms/validates DTOs
3. Controller receives validated request
4. Controller invokes Service via DI
5. Service calls PrismaClient to query/update DB
6. PrismaClient communicates with PostgreSQL
7. DB response bubbles up through Service → Controller
8. Exception Filter catches unhandled errors, formats response
9. Response returned to Client
c. Architectural Patterns & Principles
• Modular Monolith: logically separated modules, each with its own controller/service
• Dependency Injection: Nest’s built-in DI container wires controllers, services, PrismaClient
• Layered Architecture: Controllers (API layer) → Services (Business layer) → Prisma/DB (Data layer)
• Validation & Error Handling: DTOs with class-validator, global exception filters
• Configuration & Migrations: Prisma schema + migration scripts for reproducible DB state
d. Key Technologies & Frameworks
• NestJS (modules, controllers, providers)
• TypeScript + Node.js
• Prisma ORM, Neon Postgres
• class-validator & class-transformer
• Jest (unit/e2e testing)
• Middleware: CORS, rate limiting libraries