Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

NestJS ValidationPipe leaves body numbers as strings

Error@Param('id') id arrives as the string '5' although typed number

Short answer

ValidationPipe only transforms what it is told to run on. Check that the pipe is registered with transform: true, that the handler parameter is typed with a DTO class (not an interface or inline type), and remember that path and query values arrive as strings. Convert primitives with a typed parameter or ParseIntPipe.

  • Applies to NestJS 11, class-validator, class-transformer, Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Print the type of the value inside the handler. It shows at once whether you got a plain object or a DTO instance.

    console.log(dto.constructor.name, typeof dto.age);
  2. 2Match what you see, then jump to its fix

    1. 1dto.constructor.name is 'Object'The pipe is not registered, or transform is offFix
    2. 2@Param('id') id gives '5', not 5A path or query value is still a stringFix
    3. 3Validation never runs and the value stays a plain objectThe body parameter is typed with an interface, not a classFix

What does the error look like?

  • @Param('id') id arrives as the string '5' although typed number
  • The DTO parameter is a plain Object, not an instance of the DTO class

Cause 1 of 3

The pipe is not registered, or transform is off

1Check

The docs say payloads arrive as plain objects, and transform: true makes the pipe turn them into DTO class instances. Find where ValidationPipe is created.

grep -rn "ValidationPipe" src/

2Fix

Enable it globally in main.ts, or for one method with UsePipes.

app.useGlobalPipes(new ValidationPipe({ transform: true }));

3Verify

Send a request and log the constructor name again; it should be the DTO class.

curl -s -X POST localhost:3000/items -H 'Content-Type: application/json' -d '{"age":5}'

Confirmed by docs.nestjs.com

Did this fix it?

Cause 2 of 3

A path or query value is still a string

1Check

The docs state path and query parameters always arrive as strings. With transform on, the pipe converts them from the declared type; with it off you must convert them yourself.

grep -rn "@Param\|@Query" src/

2Fix

Declare the parameter type with transform enabled, or use ParseIntPipe explicitly.

@Get(':id')
find(@Param('id', ParseIntPipe) id: number) {
  return this.service.find(id);
}

3Verify

Request /items/5 and check typeof id is 'number'.

curl -s localhost:3000/items/5

Confirmed by docs.nestjs.com

Did this fix it?

Cause 3 of 3

The body parameter is typed with an interface, not a class

1Check

Interfaces are erased when TypeScript compiles, so the pipe sees the type as Object and skips it. Only a class gives it something to convert to.

grep -rn "@Body()" src/

2Fix

Declare the DTO as a class with class-validator decorators and use it as the parameter type.

export class CreateItemDto {
  @IsInt()
  age: number;
}

@Post()
create(@Body() dto: CreateItemDto) {}

3Verify

Post a bad value and expect a 400 response from the pipe.

curl -s -X POST localhost:3000/items -H 'Content-Type: application/json' -d '{"age":"abc"}'

Confirmed by docs.nestjs.com

Did this fix it?

How do I stop it coming back?

  • Register ValidationPipe once, globally, so every route behaves the same.
  • Type handler parameters with DTO classes; interfaces are erased at runtime and cannot be used.
  • Add one request-level test per DTO that checks types after the pipe.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

NestJS GraphQL cannot work out the output type of a field or query

Cannot determine a GraphQL output type for the "<name>". Make sure your class is decorated with an appropriate decorator.

In code-first mode Nest reads TypeScript types through decorators, and arrays, promises and unions disappear at runtime.

2 causes, each with a fix

Back end

IntelliJ IDEA breakpoints are ignored in a NestJS app

No 'Debugger listening' line appears when the NestJS app starts

IntelliJ can only debug a NestJS app when the Node.js process runs with the inspector on and the IDE attaches to its port.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.