How to Fix Type Mismatch in NestJS

Resolving Type Mismatch in NestJS

NestJS uses class-validator and class-transformer for DTO validation. Type mismatches occur when incoming request data doesn't match your DTO class definitions.

Common Causes

• Missing @Type() decorator on nested objects
• Client sending wrong data types for fields
• Pipes not configured to transform primitives

Solution

Decorate your DTOs properly and enable global validation:

import { IsInt, IsString, ValidateNested } from 'class-validator';
import { Type } from 'class-transformer';

class AddressDto {
  @IsString()
  street: string;

  @IsString()
  city: string;
}

class CreateUserDto {
  @IsString()
  name: string;

  @IsInt()
  age: number;

  @ValidateNested()
  @Type(() => AddressDto)
  address: AddressDto;
}

// main.ts
app.useGlobalPipes(new ValidationPipe({
  transform: true,
  whitelist: true,
}));

The transform: true option auto-converts primitive types, so "42" in a query param becomes 42 when the DTO expects a number.

Avoiding Recurrence

Once you fix this error, add a regression test that reproduces the exact scenario. Document the root cause in your team's knowledge base so others can recognize the pattern. Configure monitoring alerts for early detection if the issue appears again in a different part of the codebase.

Bugsly for NestJS

Bugsly captures validation failures with the DTO class name, field, and the actual value received. This helps you quickly identify which clients are sending malformed requests.