[Question] Why not get a promise as a param instead of a function?

[eduardosada]

Why is this better?

const [error, user] = await until(() => fetchUser(id))

instead of this?

const [error, user] = await until(fetchUser(id))

[karlhorky]

Could probably work, there are a bunch of alternatives that do that:

• https://gist.github.com/karlhorky/3593d8cd9779cf9313f9852c59260642
• https://www.npmjs.com/package/try-to-catch
• https://www.npmjs.com/package/@casperengl/try-catch
• https://www.npmjs.com/package/try-catch-js
• https://www.npmjs.com/package/trycatch (closest to ES Proposal, also supports synchronous mode)
• https://www.npmjs.com/package/await-to-js
• https://www.npmjs.com/package/try-catch-expression
• https://www.npmjs.com/package/try-catch
• https://www.npmjs.com/package/try.catch

[kettanaito]

I like how passing a function creates a new scope in which a promise is created, as opposed to accepting a promise potentially created elsewhere. I don't have any hard opinion on this, so if you think an alternative call signature makes more sense, I wouldn't mind changing it.

[kettanaito]

Accepting a new function also means you can group asynchronous operations, which you cannot otherwise do:

await until(async () => {
  await one()
  await two()
  await three()
})

Promise.all() and friends do not provide you with the equivalent degree of control (e.g. await one then check its result before firing off two).