Exception mapping interceptor in NestJS - Performance & Optimization

Performance: Exception mapping interceptor

MEDIUM IMPACT

This affects server response time and client perceived latency by how exceptions are caught and transformed before sending responses.

Handling exceptions to send user-friendly error responses

NestJS

import { CallHandler, ExecutionContext, Injectable, NestInterceptor } from '@nestjs/common';
import { Observable, throwError } from 'rxjs';
import { catchError } from 'rxjs/operators';

@Injectable()
export class GoodExceptionInterceptor implements NestInterceptor {
  intercept(context: ExecutionContext, next: CallHandler): Observable<any> {
    return next.handle().pipe(
      catchError(err => {
        // Non-blocking error mapping
        const mappedError = new Error('Mapped error');
        return throwError(() => mappedError);
      }),
    );
  }
}

Avoids blocking operations, allowing the event loop to remain free and responses to be sent faster.

📈 Performance GainNon-blocking error handling improves INP and reduces server response delays

Handling exceptions to send user-friendly error responses

NestJS

import { CallHandler, ExecutionContext, Injectable, NestInterceptor } from '@nestjs/common';
import { Observable, throwError } from 'rxjs';
import { catchError } from 'rxjs/operators';

@Injectable()
export class BadExceptionInterceptor implements NestInterceptor {
  intercept(context: ExecutionContext, next: CallHandler): Observable<any> {
    return next.handle().pipe(
      catchError(err => {
        // Synchronously blocking operation
        const end = Date.now() + 100;
        while (Date.now() < end) {}
        return throwError(() => new Error('Mapped error'));
      }),
    );
  }
}

Blocking the event loop inside the interceptor delays all other requests and increases server response time.

📉 Performance CostBlocks event loop for 100ms per error, increasing INP and overall latency

Performance Comparison

Pattern	Event Loop Blocking	Response Delay	Server Load	Verdict
Blocking synchronous error mapping	Yes, blocks event loop	High delay per error	Increases under load	[X] Bad
Non-blocking asynchronous error mapping	No blocking	Minimal delay	Efficient under load	[OK] Good

Rendering Pipeline

Exception mapping interceptors run on the server before sending the HTTP response. They catch errors from request handlers and transform them. Blocking operations here delay the server's response, increasing client wait time.

→Server Processing

→Response Generation

⚠️ BottleneckBlocking synchronous code inside the interceptor delays response generation

Core Web Vital Affected

INP

This affects server response time and client perceived latency by how exceptions are caught and transformed before sending responses.

Optimization Tips

1Never block the Node.js event loop inside interceptors.

2Use asynchronous error handling to keep server responses fast.

3Monitor server response times to catch slow exception mapping.

Performance Quiz - 3 Questions

What is the main performance risk of blocking synchronous code inside an exception mapping interceptor?

A It causes layout shifts in the browser

B It blocks the event loop, delaying all server responses

C It increases CSS paint time on the client

D It reduces the bundle size

DevTools: Network and Performance panels

How to check: Use Network panel to measure response times for requests that trigger errors. Use Performance panel to check if server responses are delayed due to blocking code.

What to look for: Look for long server response times and event loop blocking indicators in Performance traces.

Practice

1. What is the main purpose of an ExceptionMappingInterceptor in NestJS?

easy

A. To catch exceptions and transform them into user-friendly responses

B. To log all incoming HTTP requests

C. To validate incoming request data automatically

D. To manage database connections

Solution

1. Step 1: Understand the role of interceptors

   Interceptors in NestJS can modify requests or responses and handle errors.

2. Step 2: Identify the function of exception mapping

   An ExceptionMappingInterceptor specifically catches exceptions and converts them into consistent, user-friendly API responses.

3. Final Answer:

   To catch exceptions and transform them into user-friendly responses -> Option A

4. Quick Check:

   Exception mapping = user-friendly error response [OK]

Hint: Exception interceptors catch errors and format responses [OK]

Common Mistakes:

• Confusing interceptors with middleware for logging
• Thinking interceptors validate data automatically
• Assuming interceptors manage database connections

2. Which RxJS operator is commonly used inside an ExceptionMappingInterceptor to handle errors?

easy

A. map

B. filter

C. tap

D. catchError

Solution

1. Step 1: Recall RxJS operators for error handling

   The catchError operator is designed to catch errors in an observable stream.

2. Step 2: Match operator to interceptor usage

   ExceptionMappingInterceptor uses catchError to catch exceptions and transform them.

3. Final Answer:

   catchError -> Option D

4. Quick Check:

   RxJS error handling = catchError [OK]

Hint: Use catchError to catch and transform errors in observables [OK]

Common Mistakes:

• Using map which transforms data but doesn't catch errors
• Confusing filter with error handling
• Using tap which is for side effects, not error catching

3. Given this ExceptionMappingInterceptor code snippet, what will be the output if the handler throws an error?

intercept(context, next) {
  return next.handle().pipe(
    catchError(err => {
      return throwError(() => new BadRequestException('Mapped error'));
    }),
  );
}

medium

A. The original error is sent to the client

B. No error is sent; the request succeeds silently

C. A BadRequestException with message 'Mapped error' is sent to the client

D. A syntax error occurs and the app crashes

Solution

1. Step 1: Analyze the catchError block

   When an error occurs, catchError catches it and returns a new BadRequestException with a custom message.

2. Step 2: Understand the effect on the client response

   The client receives the new BadRequestException with message 'Mapped error' instead of the original error.

3. Final Answer:

   A BadRequestException with message 'Mapped error' is sent to the client -> Option C

4. Quick Check:

   Error replaced by BadRequestException [OK]

Hint: catchError replaces original error with mapped exception [OK]

Common Mistakes:

• Thinking original error passes through unchanged
• Assuming no error is sent and request succeeds
• Confusing syntax error with runtime error

4. Identify the error in this ExceptionMappingInterceptor code:

intercept(context, next) {
  return next.handle().pipe(
    catchError(err => {
      throw new HttpException('Error occurred', 400);
    }),
  );
}

medium

A. No error; code is correct

B. Using throw inside catchError instead of returning an observable error

C. Incorrect status code 400 instead of 500

D. Missing import for HttpException

Solution

1. Step 1: Understand catchError usage

   Inside catchError, you must return an observable error, not throw an error directly.

2. Step 2: Identify correct error handling

   The code should return throwError(() => new HttpException(...)) instead of throwing.

3. Final Answer:

   Using throw inside catchError instead of returning an observable error -> Option B

4. Quick Check:

   catchError must return observable error, not throw [OK]

Hint: Return throwError inside catchError, don't throw directly [OK]

Common Mistakes:

• Throwing error directly inside catchError
• Ignoring observable error return requirement
• Assuming status code 400 is wrong here

5. You want to create an ExceptionMappingInterceptor that converts all QueryFailedError exceptions into BadRequestException with a custom message, but lets other exceptions pass unchanged. Which code snippet correctly implements this behavior?

hard

A. return next.handle().pipe(catchError(err => {
if (err instanceof QueryFailedError) {
return throwError(() => new BadRequestException('Invalid query'));
}
return throwError(() => err);
}));

B. return next.handle().pipe(catchError(err => {
if (err instanceof QueryFailedError) {
throw new BadRequestException('Invalid query');
}
throw err;
}));

C. return next.handle().pipe(catchError(err => {
if (err.name === 'QueryFailedError') {
return new BadRequestException('Invalid query');
}
return err;
}));

D. return next.handle().pipe(catchError(err => {
if (err instanceof BadRequestException) {
return throwError(() => new QueryFailedError());
}
return throwError(() => err);
}));

Solution

1. Step 1: Check error type and return observable error

   The interceptor must check if the error is a QueryFailedError instance and return a new BadRequestException wrapped in throwError.

2. Step 2: Pass other errors unchanged as observable errors

   Other errors must be re-thrown as observable errors using throwError to keep the stream consistent.

3. Final Answer:

   Option A correctly checks error type and returns observable errors properly -> Option A

4. Quick Check:

   Use instanceof + throwError for error mapping [OK]

Hint: Use instanceof and return throwError for mapped and original errors [OK]

Common Mistakes:

• Throwing errors directly inside catchError
• Returning error objects instead of observable errors
• Checking error name string instead of instanceof
• Swapping error types incorrectly