Advanced Web's resource offers insights, tutorials, and resources for web developers and designers. Readers can learn about advanced web technologies, front-end frameworks, and web design trends. With articles, tutorials, and case studies, Advanced Web provides  guidance and expertise for building  web applications and user experiences.

Advanced Web Machinery

Using `return await` in JavaScript is essential for proper error handling with try..catch and ensuring cleanups in try..finally blocks. It stops function execution, allowing catch blocks to handle errors and ensuring resource cleanups are performed as expected.

JavaScript best practice: use return await

Using return await is a terrible idea for every case. It is very specific.
It basically wraps your promise in a promise as Async function are resolving in a promise already :
Please, never write something like this :
const helloWorld = async () =&gt; {
return await asyncHello(“World”);
}
// Hello World
The Await is just totally useless. You create a promise that wait for a promise to resolve, just for it to resolve. You’re contributing to callback hell
Return await is basically an anti-pattern, and a common misunderstanding of promises behaviour in the ecosystem. (and this is why it is targetted by linters)
If you want to return await, with a special case like this try/catch block, there’s a meaning for it. But promoting two liners like the one stated previously as a best practice, no way josé.

Hey, just a heads up, this isn’t really a best practice, it’s more like the basics! Since we’ve got an async function, all we need to do is toss an await in there.
Oh, and sorry if I might’ve misunderstood your article. Let me know if I got it wrong!

This kind of post should be deleted.
This is not even misleading, but just a lie.

that not true, if you want try catch just do at upperlevel, no need to await a promise except you really need it, like try catch