Fix BadRequestException: Validation failed (numeric string is expected) in NestJS

This error occurs when a NestJS validation pipe rejects input that does not match the expected type or DTO constraints. Common causes include passing a string where a number is expected, missing required fields, or invalid enum values. Fix it by ensuring client input matches the DTO schema and pipe configuration.

Reading the Stack Trace

Here's what each line means:

• at ParseIntPipe.transform (node_modules/@nestjs/common/pipes/parse-int.pipe.js:31:24): The ParseIntPipe tried to convert the input to an integer but the value was not a valid numeric string.
• at PipesConsumer.applyPipes (node_modules/@nestjs/core/pipes/pipes-consumer.js:30:17): NestJS applies all registered pipes in order before the route handler executes.
• at RouterExplorer.executePipeline (node_modules/@nestjs/core/router/router-execution-context.js:174:41): The execution pipeline runs pipes after guards but before the controller method, rejecting invalid input early.

Common Causes

@Get(':id')
findOne(@Param('id', ParseIntPipe) id: number) {
  return this.service.findOne(id);
}
// GET /users/abc -> Validation failed

export class CreateUserDto {
  @IsNotEmpty()
  name: string;

  @IsEmail()
  email: string;
}
// Client sends: { name: 'Alice' } -> email is missing

// main.ts - no global pipe configured
const app = await NestFactory.create(AppModule);
await app.listen(3000);

The Fix

Customize the ParseIntPipe exception factory to return a human-readable error message. Apply ValidationPipe globally so all DTOs are validated automatically. Use whitelist to strip unexpected properties and transform to auto-cast types.

import { Controller, Get, Param, ParseIntPipe } from '@nestjs/common';

@Controller('users')
export class UserController {
  @Get(':id')
  findOne(@Param('id', ParseIntPipe) id: number) {
    return this.userService.findOne(id);
  }
}

import { Controller, Get, Param, ParseIntPipe, BadRequestException } from '@nestjs/common';

@Controller('users')
export class UserController {
  @Get(':id')
  findOne(
    @Param('id', new ParseIntPipe({
      exceptionFactory: () => new BadRequestException('User ID must be a valid integer'),
    }))
    id: number,
  ) {
    return this.userService.findOne(id);
  }
}

// In main.ts - apply global validation pipe
// app.useGlobalPipes(new ValidationPipe({
//   whitelist: true,
//   forbidNonWhitelisted: true,
//   transform: true,
// }));

Testing the Fix

import { Test, TestingModule } from '@nestjs/testing';
import { UserController } from './user.controller';
import { UserService } from './user.service';
import { BadRequestException } from '@nestjs/common';

describe('UserController', () => {
  let controller: UserController;

  beforeEach(async () => {
    const module: TestingModule = await Test.createTestingModule({
      controllers: [UserController],
      providers: [
        { provide: UserService, useValue: { findOne: jest.fn().mockResolvedValue({ id: 1 }) } },
      ],
    }).compile();

    controller = module.get<UserController>(UserController);
  });

  it('returns a user for a valid numeric ID', async () => {
    const result = await controller.findOne(1);
    expect(result).toEqual({ id: 1 });
  });

  it('ParseIntPipe rejects non-numeric strings', () => {
    const pipe = new (require('@nestjs/common').ParseIntPipe)({
      exceptionFactory: () => new BadRequestException('User ID must be a valid integer'),
    });
    expect(() => pipe.transform('abc', { type: 'param' })).rejects.toThrow('User ID must be a valid integer');
  });
});

Run your tests:

npm test

Pushing Through CI/CD

git checkout -b fix/nestjs-pipe-validation,git add src/user/user.controller.ts src/user/__tests__/user.controller.spec.ts src/main.ts,git commit -m "fix: add descriptive validation errors and global ValidationPipe",git push origin fix/nestjs-pipe-validation

Your CI config should look something like this:

name: CI
on:
  pull_request:
    branches: [main]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm test -- --coverage
      - run: npm run build

The Full Manual Process: 18 Steps

Here's every step you just went through to fix this one bug:

1. Notice the error alert or see it in your monitoring tool
2. Open the error dashboard and read the stack trace
3. Identify the file and line number from the stack trace
4. Open your IDE and navigate to the file
5. Read the surrounding code to understand context
6. Reproduce the error locally
7. Identify the root cause
8. Write the fix
9. Run the test suite locally
10. Fix any failing tests
11. Write new tests covering the edge case
12. Run the full test suite again
13. Create a new git branch
14. Commit and push your changes
15. Open a pull request
16. Wait for code review
17. Merge and deploy to production
18. Monitor production to confirm the error is resolved

Total time: 30-60 minutes. For one bug.

npm install bugstack-sdk

import { initBugStack } from 'bugstack-sdk'

initBugStack({ apiKey: process.env.BUGSTACK_API_KEY })

Deploying the Fix (Manual Path)

1. Configure ValidationPipe globally in main.ts.
2. Add descriptive exception factories to built-in pipes.
3. Add class-validator decorators to all DTOs.
4. Run tests to verify validation behavior.
5. Open a PR, merge after CI, and verify in staging.

Frequently Asked Questions