Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Aprenda Handling Errors in Nest.js | Section
Building Backend Applications with Nest.js

bookHandling Errors in Nest.js

Deslize para mostrar o menu

Errors are part of any backend application. Nest.js provides a simple way to handle them using built-in exceptions.

Instead of returning plain values, you can throw an exception when something goes wrong.

Here is an example:

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

@Controller('users')
export class UsersController {
  @Get(':id')
  getUser() {
    throw new NotFoundException('User not found');
  }
}

In this example:

  • NotFoundException: represents a 404 error;
  • The request is stopped and an error response is returned.

Nest.js includes several built-in exceptions:

  • NotFoundException: resource not found;
  • BadRequestException: invalid request;
  • UnauthorizedException: access denied.

You can use these exceptions to clearly describe what went wrong.

Throwing exceptions makes your API more predictable and easier to debug.

question mark

What should you do when an error occurs in a Nest.js controller?

Selecione a resposta correta

Tudo estava claro?

Como podemos melhorá-lo?

Obrigado pelo seu feedback!

Seção 1. Capítulo 20

Pergunte à IA

expand

Pergunte à IA

ChatGPT

Pergunte o que quiser ou experimente uma das perguntas sugeridas para iniciar nosso bate-papo

Seção 1. Capítulo 20
some-alt