until

Gracefully handle Promises using async/await without try/catch.

Error handling
open-draft/until@open-draft/until

README

until


Gracefully handle a Promise using async/await.

Why?


With the addition of async/await keywords in ECMAScript 2017 the handling of Promises became much easier. However, one must keep in mind that the await keyword provides no standard error handling API. Consider this usage:

  1. ```js
  2. function getUser(id) {
  3.   const data = await fetchUser(id)
  4.   // Work with "data"...
  5. }
  6. ```

In case fetchUser() throws an error, the entire getUser() function's scope will terminate. Because of this, it's recommended to implement error handling using try/catch block wrapping await expressions:

  1. ```js
  2. function getUser(id){
  3.   let data = null

  5.   try {
  6.     data = await asyncAction()
  7.   } catch (error) {
  8.     console.error(error)
  9.   }

  11.   // Work with "data"...
  12. }
  13. ```

While this is a semantically valid approach, constructing try/catch around each awaited operation may be tedious and get overlooked at times. Such error handling also introduces separate closures for execution and error scenarios of an asynchronous operation.

This library encapsulates the try/catch error handling in a utility function that does not create a separate closure and exposes a NodeJS-friendly API to work with errors and resolved data.

Getting started


Install


  1. ```bash
  2. npm install @open-draft/until
  3. ```

Usage


  1. ```js
  2. import { until } from '@open-draft/until'

  4. async function getUserById(id) {
  5.   const { error, data } = await until(() => fetchUser(id))

  7.   if (error) {
  8.     return handleError(error)
  9.   }

  11.   return data
  12. }
  13. ```

Usage with TypeScript


  1. ```ts
  2. import { until } from '@open-draft/until'

  4. interface User {
  5.   firstName: string
  6.   age: number
  7. }

  9. interface UserFetchError {
  10.   type: 'FORBIDDEN' | 'NOT_FOUND'
  11.   message?: string
  12. }

  14. async function getUserById(id: string) {
  15.   const { error, data } = await until<UserFetchError, User>(() => fetchUser(id))

  17.   if (error) {
  18.     return handleError(error.type, error.message)
  19.   }

  21.   return data.firstName
  22. }
  23. ```

Frequently asked questions


Why does until accept a function and not a Promise directly?


This has been intentionally introduced to await a single logical unit as opposed to a single Promise.

  1. ```js
  2. // Notice how a single "until" invocation can handle
  3. // a rather complex piece of logic. This way any rejections
  4. // or exceptions happening within the given function
  5. // can be handled via the same "error".
  6. const { error, data } = until(async () => {
  7.   const user = await fetchUser()
  8.   const nextUser = normalizeUser(user)
  9.   const transaction = await saveModel('user', user)

  11.   invariant(transaction.status === 'OK', 'Saving user failed')

  13.   return transaction.result
  14. })

  16. if (error) {
  17.   // Handle any exceptions happened within the function.
  18. }
  19. ```

Why does until return an object and not an array?


The until function used to return an array of shape [error, data] prior to 2.0.0. That has been changed, however, to get proper type-safety using discriminated union type.

Compare these two examples:

  1. ```ts
  2. const [error, data] = await until(() => action())

  4. if (error) {
  5.   return null
  6. }

  8. // Data still has ambiguous "DataType | null" type here
  9. // even after you've checked and handled the "error" above.
  10. console.log(data)
  11. ```

  1. ```ts
  2. const result = await until(() => action())

  4. // At this point, "data" is ambiguous "DataType | null"
  5. // which is correct, as you haven't checked nor handled the "error".

  7. if (result.error) {
  8.   return null
  9. }

  11. // Data is strict "DataType" since you've handled the "error" above.
  12. console.log(result.data)
  13. ```

It's crucial to keep the entire result of the Promise in a single variable and not destructure it. TypeScript will always keep the type of error and data as it was upon destructuring, ignoring any type guards you may perform later on.


Special thanks


- giuseppegurgone for the discussion about the originaluntil API.