NestJS CI/CD Pipelines — Enterprise Node.js Deserves Enterprise-Grade Deployment

NestJS uses TypeScript decorators extensively for dependency injection, routing, and validation. The compiled JavaScript output depends on emitDecoratorMetadata and experimentalDecorators being set correctly in tsconfig.json. A misconfigured TypeScript compilation can produce code that looks correct but fails at runtime with cryptic DI errors.

NestJS applications commonly use Prisma or TypeORM for database access. Both ORMs have their own migration systems that need to be integrated into the deployment pipeline. Prisma's prisma generate step must run after npm install to generate the client, and the generated client must be included in the Docker image. Missing this step is the most common NestJS deployment failure we see.

Testing NestJS involves its own testing module system. The Test.createTestingModule() pattern requires careful mock provider setup, and integration tests that hit a real database need the full module tree to be initialized. Getting this right in CI, with proper database cleanup between test suites, takes deliberate configuration.

We configure the pipeline to run tsc --noEmit separately from the build step to catch type errors without producing output. The actual build uses nest build (or swc for faster compilation) to produce the dist/ directory. We verify that decorator metadata is emitted correctly by running a smoke test against the compiled output.

Testing uses Jest with NestJS's testing utilities. Unit tests mock providers using Test.createTestingModule and run in milliseconds. Integration tests spin up the full application with app.init() against a PostgreSQL test database, running Prisma migrations before the test suite and resetting data between tests using transactions. E2E tests use Supertest to hit actual HTTP endpoints.

The Docker build runs npm ci, prisma generate, and nest build in the builder stage. The production stage copies only dist/, node_modules/ (pruned of dev dependencies), and the Prisma client. We use node:20-alpine with a non-root user. Database migrations run as a pre-deploy job with prisma migrate deploy, which applies pending migrations without generating new ones.

A NestJS-specific CI/CD pipeline:

• TypeScript compilation — type checking and build with decorator metadata validation
• Jest test automation — unit, integration, and E2E tests with NestJS testing module
• Prisma/TypeORM integration — client generation and migration automation
• SWC compilation — optional 20x faster builds using SWC instead of tsc
• Docker optimization — multi-stage build with pruned node_modules
• Health check endpoints — NestJS Terminus module wired into deployment validation
• Swagger/OpenAPI — API documentation generated and validated in CI