DEV Community

'return await' in a try/catch

Daniel Bellmas on December 09, 2023

This might sound weird to you, the first thing that comes to mind is: 'Eslint will tell me to remove the await, there is no need for an await after...

Read full post

Joshua Baker • Dec 10 '23

In my opinion, you should almost never return a promise from an async function. You should return await instead. Not only does that cover this case naturally, it also improves async stack traces for debugging.

Martin Omander • Dec 11 '23

Returning a promise from an async function is still needed if you want to run several operations in parallel, isn't it? That optimization comes up fairly frequently in my code when I tune its performance.

Daniel Hillmann • Dec 11 '23 • Edited

Why can you not run multiple functions in parallel if they're awaited? 🤔

async function getWebpage(url) {
  try {
    const { data: webpage } = await axios.get(url);

    return webpage;
  } catch (err) {
     // a request failed
     // will make Promise.all throw
  }
}
const results = await Promise.all([
  getWebpage('https://google.com'),
  getWebpage('https://facebook.com')
]);
// Executed in parallel
// results[0] = google
// results[1] = facebook

Daniel Bellmas • Dec 11 '23 • Edited

That's right, that's a good use case for returning a promise without await, thanks for the clarification 🙏

Mike Stemle • Dec 16 '23

An async function, definitionally and per spec, always returns a Promise.

Working proof: replit.com/@manchicken/What-async-...

Brian Morearty • Dec 11 '23

I think it’s pretty common to call another async function at the end of your async function and return the result. As in the example. In that case there’s no way around it.

Daniel Bellmas • Dec 11 '23 • Edited

Interesting, Are you disabling the Eslint rule then?

Mike Talbot ⭐ • Dec 14 '23 • Edited

The rule definition is as follows, personally I think it's rather dangerous as the most likely effect of applying it is that exceptions end up being incorrectly handled. Now this happens because initially there is no try/catch so eslint complains about the await and then the developer removes it and later adds a try/catch block for errors - if it had been there from the start then the await would not have been linted.

Disallows unnecessary return await (no-return-await)

Inside an async function, return await is useless. Since the return value of an async function is always wrapped in Promise.resolve, return await doesn’t actually do anything except add extra time before the overarching Promise resolves or rejects. This pattern is almost certainly due to programmer ignorance of the return semantics of async functions.

Daniel Bellmas • Dec 15 '23

I agree, thanks for the awesome explanation Mike!

Yeom suyun • Dec 10 '23

Async await is more convenient than Promise chains, but I don't see why you wouldn't use Promise.catch in the example.

Daniel Bellmas • Dec 10 '23

You could, this example is pretty simple so you're right, but for more complex logic try and catch is usually more convinient

Martin Omander • Dec 11 '23

Great post! It was short, easy to understand, and easy to see the advantage of organizing the code you propose.

Daniel Bellmas • Dec 11 '23

Thank you Martin! I appreciate it :)

Shameel Uddin • Dec 10 '23

I could not fully understand the purpose if this blog.

Michael Kochell • Dec 11 '23

Yeah I don't get the pros and cons of using it. I didn't even know you could do that, and I'm unsure exactly why I would or would not want to in the context of a try block, based on reading this blog post.

Daniel Bellmas • Dec 11 '23

The main pro is being able to catch the error. I don’t see a con.
This is a specific use case for when you return a promise

Daniel Bellmas • Dec 11 '23

To share a bug I had where I didn’t use await when I returned a promise and I couldn’t understand why my console log in the catch didn’t print