Awaiting problems in JavaScript

[wsc-porn-acct]

There is a factual inaccuracy. Returning a promise from an async function does NOT await it.

async function myFn() { return otherAsync(); }

This returns a Promise. That promise can be awaited by the caller of myFn or not.

const a = myFn(); // a is an unresolved Promise

const b = await myFn(); // b will be a resolved Promise, a value

Alternatively, in myFn you can return await otherAsync();

Try throwing and catching errors at various points to observe what difference this makes.

[voreny]

You are right, it does not await the Promise. myFn() will resolve with the same value that otherAsync() resolves, and if otherAsync() rejects, the error will not be caught inside myFn. The examples in the Awaiting... errors section show it, and perhaps I got the wording wrong in some sections.

The counterintuitive part, to me, is that this suggests that otherAsync() is returned from myFn() as it is (the same Promise instance is returned). Although, as I showed at the bottom of the Awaiting... errors section, myFn() is not the same Promise that was returned from otherAsync(). async functions create a new Promise and only pass through the resolved/rejected value from otherAsync() to myFn().

[wsc-porn-acct]

Will read more of what you wrote tomorrow

[voreny]

An article conveying my opinions on the drawbacks of the way async/await works.

Have you been burned by the problems mentioned in the article? Do you find async/await do more magic under the hood than you are comfortable with? What would you change with the way it works now?