ES8 Immediately invoked async function expression

by

Is this ‘a thing’?

Yes. It comes up every now and then, e.g. here. They’re known as IIAFEs 🙂
If you want to put focus on the arrow, you could also call them IIAAFs.

Are there pitfalls here I should be aware of?

Whenever you call a promise-returning function and don’t return the result to somewhere else, you are responsible for the promise yourself – which means that you have to handle errors from it. So the pattern should in general look like

(async () => {
    …
})().catch(err => {
    console.error(err);
});

if you don’t want to concern yourself with unhandled-rejection events.

What’s the lowdown on use of async/await in these kind of situations?

Not much, compared to the then version. However, you say “the external lib does not expect a return value from this callback“, which might hint at the library’s incompatibility with asynchronous callbacks, so beware what you are doing when. It also might depend on exceptions being thrown synchronously from the callback, so it all depends on what the library expects here (and if there are no expectations, whether that may change in the future). You don’t want future incompatibilities in case the library will start to treat promise return values specially.

However, I would still recommend the second pattern that directly passes the async function directly as the callback because of its better readability. If you want to avoid returning a promise to the library, create a helper function that wraps the callback:

function toVoid(fn) {
    return (...args) => void fn(...args);
}
function promiseToVoid(fn) {
    return (...args) => void fn(...args).catch(console.error);
}

which you could use like this:

chan.consume(queue, toVoid(async (msg) => {
     … // use `await` freely
}));

More Related Contents:

  1. Combination of async function + await + setTimeout
  2. Use async await with Array.map
  3. Correct Try…Catch Syntax Using Async/Await
  4. Waiting for more than one concurrent await operation
  5. async/await always returns promise
  6. How can I use async/await at the top level?
  7. Using async/await with a forEach loop
  8. How to “await” for a callback to return?
  9. Why are await and async valid variable names?
  10. Is there a way to wrap an await/async try/catch block to every function?
  11. How to use ES8 async/await with streams?
  12. Async/Await inside Array#map()
  13. async/await inside arrow functions (Array#map/filter)
  14. Is async await truly non-blocking in the browser?
  15. ES2017 – Async vs. Yield
  16. Are there performance concerns with `return await`?
  17. Limited parallelism with async/await in Typescript/ES7
  18. Await is a reserved word error inside async function
  19. for await of VS Promise.all
  20. try..catch not catching async/await errors
  21. How to return an Ajax result using async/await? [duplicate]
  22. Async / await vs then which is the best for performance?
  23. Use Async/Await with Axios in React.js
  24. What is the benefit of prepending async to a function that returns a promise?
  25. Using for await…of with synchronous iterables
  26. How to use Array.prototype.filter with async?
  27. How does javascript async/await actually work?
  28. Await an iterative function without delimiter in JS
  29. Cypress.io How to handle async code
  30. ASYNC / AWAIT SyntaxError: await is only valid in async functions and the top level bodies of modules

Leave a Comment