I do not understand why it is necessary to have the async keyword before the function keyword. For the same reason that we have the * symbol before generator functions: They mark the function as extraordinary. They are quite similar in that regard – they add a visual marker that the body of this function … Read more
if some function just returns Promise and doesn’t awaiting for anything, should I mark the function as async? I would say you shouldn’t. The purpose of async/await is to create (and resolve) the promise for you; if you already have a promise to return, then async/await won’t give you any benefit for that function. Both … Read more
I prefer to assign the first result to an intermediate variable, I personally find it more readable. If you prefer, you can await in an expression, no need to assign it. All you have to do is to use parentheses. See my example: const foo = await (await myAsyncFunction()).somethingElseAsync() Or if you want to call … Read more
this should work: async () => { try { const result1 = await firstAsynchronousFunction(); const result2 = await secondAsynchronousFunction(result1); console.log(result2); } catch(err) { throw new Error(`Something failed`); } finally { console.log(`All Tasks are Done`); } }
You have to use either then or await not both as shown below: If using then created () { this.getA().then((result) => { console.log(1) console.log(2) this.getB() }) }, methods : { getA () { return $axios.post(`/getA`,params); }, getB (){ console.log(3) } } If using await async created (){ await this.getA() console.log(1) console.log(2) this.getB() }, methods : … Read more
As of node ^10, you can use the following flag when starting the repl: node –experimental-repl-await $ await myPromise()
Just as its name implies, the await keyword will cause the function to “wait” until the corresponding promise resolves before executing the next line. The whole point of await is to provide a way to wait for an asynchronous operation to complete before continuing. The difference between this and blocking code is that the world … Read more
Reserved keywords cannot be used as identifiers (variable names). Unlike most other special Javascript words (like those listed in the question, let, finally, …), await is not a reserved keyword, so using it as a variable name does not throw a SyntaxError. Why wasn’t it made into a reserved keyword when the new syntax came … Read more
TL;DR Don’t use the pattern in the question where you get the promises, and then separately wait on them; instead, use Promise.all (at least for now): const [value1, value2] = await Promise.all([getValue1Async(), getValue2Async()]); While your solution does run the two operations in parallel, it doesn’t handle rejection properly if both promises reject. Details: Your solution … Read more