NestJS中async/await的使用差异及遗漏return的进程风险问询

Great question—this is a super common gotcha when working with NestJS, especially since it’s easy to miss how the framework handles asynchronous operations under the hood. Let’s break down what’s happening with each of your code examples, and address your core concern about process termination.

First, Let’s Clarify the Three Approaches #

1. No async/await and No return (The Problematic One) #

@Post() saveClient(@Param() params, @Body() createClientDto: ClientDto) { 
  this.clientRepository.save(createClientDto); 
}

Here, this.clientRepository.save() returns a Promise, but your function immediately returns void without attaching any handlers to that Promise. Node.js detects this unhandled Promise rejection and throws the warning you saw.

Right now, this is just a warning, but as the deprecation notice states: future Node.js versions will terminate the process entirely when an unhandled Promise rejection occurs.

2. Using async/await (The Safe Approach) #

@Post() async saveClient(@Param() params, @Body() createClientDto: ClientDto) { 
  await this.clientRepository.save(createClientDto); 
}

Marking the function as async automatically wraps its return value in a Promise. Even if you don’t explicitly return anything, when the awaited Promise rejects, the async function’s returned Promise will also reject.

NestJS is designed to catch these rejected Promises from request handlers and automatically convert them into appropriate HTTP error responses (like a 500 Internal Server Error), so no unhandled rejection warning is triggered.

3. Explicitly Returning the Promise (Also Safe) #

@Post() saveClient(@Param() params, @Body() createClientDto: ClientDto) { 
  return this.clientRepository.save(createClientDto); 
}

By returning the Promise directly, you’re passing it off to NestJS. The framework will subscribe to this Promise, and if it rejects, NestJS handles the error the same way it does with async/await functions—converting it to an HTTP response instead of letting it become an unhandled rejection.

Will Missing return Cause NestJS to Terminate? #

• Right now: Probably not—you’ll just get the deprecation warning. But this is risky because the client will hang waiting for a response (until timeout), and you’ll miss clear error logging for debugging.
• In future Node.js versions: Yes, unhandled Promise rejections will terminate the Node.js process entirely, which means your NestJS app will crash.

Best Practices to Avoid This #

• Prefer async/await: It makes your code more readable, and it’s easier to add try/catch blocks if you need to handle specific errors (like returning a 400 Bad Request instead of a 500).
• Always handle Promises: Either return them or wrap them in an async function. Never leave a Promise floating without attaching a handler or passing it to the framework.

内容的提问来源于stack exchange，提问作者user2010955