File validation pipe in NestJS - Performance & Optimization

Performance: File validation pipe

MEDIUM IMPACT

This affects the server response time and user experience by validating files before processing, impacting input responsiveness and backend load.

Validating uploaded files in a NestJS backend

NestJS

import { PipeTransform, Injectable, BadRequestException, ArgumentMetadata } from '@nestjs/common';

@Injectable()
export class FileValidationPipe implements PipeTransform<Express.Multer.File> {
  async transform(value: Express.Multer.File, metadata: ArgumentMetadata) {
    if (!value) {
      throw new BadRequestException('No file provided');
    }
    // Use async checks or offload heavy validation
    if (value.size > 10 * 1024 * 1024) {
      throw new BadRequestException('File too large');
    }
    if (!['image/png', 'image/jpeg'].includes(value.mimetype)) {
      throw new BadRequestException('Invalid file type');
    }
    return value;
  }
}

Using async validation or lightweight checks prevents blocking the event loop, improving responsiveness especially under concurrent uploads.

📈 Performance GainNon-blocking validation reduces response delay by tens of milliseconds per file, improving INP

Validating uploaded files in a NestJS backend

NestJS

import { PipeTransform, Injectable, BadRequestException, ArgumentMetadata } from '@nestjs/common';

@Injectable()
export class FileValidationPipe implements PipeTransform<Express.Multer.File> {
  transform(value: Express.Multer.File, metadata: ArgumentMetadata) {
    if (!value) {
      throw new BadRequestException('No file provided');
    }
    if (value.size > 10 * 1024 * 1024) { // 10MB limit
      throw new BadRequestException('File too large');
    }
    if (!['image/png', 'image/jpeg'].includes(value.mimetype)) {
      throw new BadRequestException('Invalid file type');
    }
    return value;
  }
}

Validating files synchronously in the pipe blocks the event loop if file size or type checks are expensive or if many files are processed, causing slower response times.

📉 Performance CostBlocks event loop during validation, increasing response time by tens of milliseconds per file under load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous file validation in pipe	0 (server-side)	0	0	[X] Bad
Asynchronous or lightweight validation in pipe	0 (server-side)	0	0	[OK] Good

Rendering Pipeline

File validation in NestJS runs on the server before the request handler. It affects the server's event loop and response time, impacting how quickly the client receives feedback.

→Request Parsing

→Validation

→Response Generation

⚠️ BottleneckValidation stage can block the event loop if synchronous and heavy

Core Web Vital Affected

INP

This affects the server response time and user experience by validating files before processing, impacting input responsiveness and backend load.

Optimization Tips

1Avoid synchronous heavy validation in NestJS pipes to keep the event loop free.

2Use asynchronous or lightweight checks for file size and type validation.

3Monitor server response times during file uploads to detect blocking validation.

Performance Quiz - 3 Questions

What is the main performance risk of synchronous file validation in a NestJS pipe?

A It blocks the event loop, delaying server responses

B It increases DOM reflows on the client

C It causes large CSS paint costs

D It adds extra bundle size to the frontend

DevTools: Network

How to check: Open DevTools, go to Network tab, upload a file, and observe the request timing and response time.

What to look for: Look for long server response times indicating blocking validation; faster responses indicate efficient validation.

Practice

1. What is the main purpose of a FileValidationPipe in NestJS?

easy

A. To upload files to a cloud storage service

B. To convert files into JSON format automatically

C. To check uploaded files for type, size, and presence before processing

D. To compress files before saving them

Solution

1. Step 1: Understand the role of validation pipes in NestJS

   Validation pipes are used to check and validate incoming data before it reaches the controller logic.

2. Step 2: Apply this to file uploads

   A FileValidationPipe specifically checks uploaded files for correct type, size, and presence to prevent bad data.

3. Final Answer:

   To check uploaded files for type, size, and presence before processing -> Option C

4. Quick Check:

   File validation = check file properties [OK]

Hint: Validation pipes check data early to keep apps safe [OK]

Common Mistakes:

• Thinking pipes upload or transform files
• Confusing validation with file storage
• Assuming pipes compress files automatically

2. Which of the following is the correct way to apply a file validation pipe to a file upload in a NestJS controller?

easy

A. @UsePipes(new FileValidationPipe()) uploadFile(@UploadedFile() file: Express.Multer.File) {}

B. @UseGuards(new FileValidationPipe()) uploadFile(@UploadedFile() file: Express.Multer.File) {}

C. @UseFilters(new FileValidationPipe()) uploadFile(@UploadedFile() file: Express.Multer.File) {}

D. @UseInterceptors(new FileValidationPipe()) uploadFile(@UploadedFile() file: Express.Multer.File) {}

Solution

1. Step 1: Identify the correct decorator for validation pipes

   In NestJS, validation pipes are applied using the @UsePipes() decorator.

2. Step 2: Match the usage with file upload

   The FileValidationPipe is a pipe, so it must be passed inside @UsePipes() to validate the uploaded file.

3. Final Answer:

   @UsePipes(new FileValidationPipe()) uploadFile(@UploadedFile() file: Express.Multer.File) {} -> Option A

4. Quick Check:

   Validation pipe = @UsePipes() [OK]

Hint: Use @UsePipes() for validation pipes, not guards or filters [OK]

Common Mistakes:

• Using @UseGuards or @UseFilters instead of @UsePipes
• Applying pipes without instantiating them
• Confusing interceptors with pipes

3. Given this pipe code snippet, what will happen if a user uploads a file larger than 1MB?

export class FileValidationPipe implements PipeTransform {
  transform(file: Express.Multer.File) {
    if (!file) throw new BadRequestException('File is required');
    if (file.size > 1_000_000) throw new BadRequestException('File too large');
    return file;
  }
}

medium

A. The pipe ignores the size and processes the file

B. The pipe accepts the file and returns it

C. The pipe throws a NotFoundException

D. The pipe throws a BadRequestException with message 'File too large'

Solution

1. Step 1: Analyze the size check in the transform method

   The pipe checks if file.size is greater than 1,000,000 bytes (1MB).

2. Step 2: Understand the exception thrown on size violation

   If the file is too large, it throws BadRequestException('File too large'), stopping the request.

3. Final Answer:

   The pipe throws a BadRequestException with message 'File too large' -> Option D

4. Quick Check:

   File size > 1MB = BadRequestException [OK]

Hint: Check exception messages in transform() for validation errors [OK]

Common Mistakes:

• Assuming the pipe accepts large files
• Confusing BadRequestException with NotFoundException
• Ignoring the file presence check

4. Identify the error in this file validation pipe code:

export class FileValidationPipe implements PipeTransform {
  transform(file: Express.Multer.File) {
    if (!file) throw new BadRequestException('File is required');
    if (file.mimetype !== 'image/png' || file.mimetype !== 'image/jpeg') {
      throw new BadRequestException('Invalid file type');
    }
    return file;
  }
}

medium

A. The mimetype check always throws because of incorrect logical operator

B. The file presence check is missing

C. The pipe does not return the file

D. The exception type is incorrect

Solution

1. Step 1: Examine the mimetype condition

   The condition uses || (OR) between two checks: file.mimetype !== 'image/png' OR file.mimetype !== 'image/jpeg'.

2. Step 2: Understand why this always triggers

   Because a file cannot be both 'image/png' and 'image/jpeg' at the same time, one of these will always be true, causing the exception every time.

3. Final Answer:

   The mimetype check always throws because of incorrect logical operator -> Option A

4. Quick Check:

   Use AND (&&) to check mimetype correctly [OK]

Hint: Use && to check if mimetype is neither png nor jpeg [OK]

Common Mistakes:

• Using || instead of && in mimetype checks
• Forgetting to return the file after validation
• Throwing wrong exception types

5. You want to create a file validation pipe that only accepts PDF files smaller than 2MB and throws a clear error if validation fails. Which of the following code snippets correctly implements this?

hard

A. export class PdfValidationPipe implements PipeTransform {
transform(file: Express.Multer.File) {
if (!file) throw new BadRequestException('File is required');
if (file.mimetype === 'application/pdf') throw new BadRequestException('Only PDFs allowed');
if (file.size > 2_000_000) throw new BadRequestException('File too large');
return file;
}
}

B. export class PdfValidationPipe implements PipeTransform {
transform(file: Express.Multer.File) {
if (!file) throw new BadRequestException('File is required');
if (file.mimetype !== 'application/pdf') throw new BadRequestException('Only PDFs allowed');
if (file.size >= 2_000_000) throw new BadRequestException('File too large');
return file;
}
}

C. export class PdfValidationPipe implements PipeTransform {
transform(file: Express.Multer.File) {
if (!file) throw new BadRequestException('File is required');
if (file.mimetype !== 'application/pdf' && file.size > 2_000_000) throw new BadRequestException('Invalid file');
return file;
}
}

D. export class PdfValidationPipe implements PipeTransform {
transform(file: Express.Multer.File) {
if (!file) throw new BadRequestException('File is required');
if (file.mimetype !== 'application/pdf' || file.size > 2_000_000) throw new BadRequestException('Invalid file');
return file;
}
}

Solution

1. Step 1: Verify correct logic for presence and mimetype

   Check if (!file) throw, then if (file.mimetype !== 'application/pdf') throw 'Only PDFs allowed'. Uses !== to reject non-PDFs.

2. Step 2: Separate size check for smaller than 2MB

   if (file.size >= 2_000_000) throw 'File too large'. Uses >= to reject 2MB or larger.

3. Step 3: Eliminate distractors

   B throws if PDF; C's && accepts non-PDF if small; D's > accepts exactly 2MB.

4. Final Answer:

   export class PdfValidationPipe implements PipeTransform { transform(file: Express.Multer.File) { if (!file) throw new BadRequestException('File is required'); if (file.mimetype !== 'application/pdf') throw new BadRequestException('Only PDFs allowed'); if (file.size >= 2_000_000) throw new BadRequestException('File too large'); return file; } } -> Option B

5. Quick Check:

   !== mimetype, >= size, separate ifs [OK]

Hint: Check each condition separately with !== and clear exceptions [OK]

Common Mistakes:

• Using === instead of !== for mimetype check
• Combining conditions incorrectly with && or ||
• Not throwing specific error messages