Last active
November 30, 2025 20:25
-
Star
(838)
You must be signed in to star a gist -
Fork
(132)
You must be signed in to fork a gist
-
-
Save t3dotgg/a486c4ae66d32bf17c09c73609dacc5b to your computer and use it in GitHub Desktop.
Theo's preferred way of handling try/catch in TypeScript
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // Types for the result object with discriminated union | |
| type Success<T> = { | |
| data: T; | |
| error: null; | |
| }; | |
| type Failure<E> = { | |
| data: null; | |
| error: E; | |
| }; | |
| type Result<T, E = Error> = Success<T> | Failure<E>; | |
| // Main wrapper function | |
| export async function tryCatch<T, E = Error>( | |
| promise: Promise<T>, | |
| ): Promise<Result<T, E>> { | |
| try { | |
| const data = await promise; | |
| return { data, error: null }; | |
| } catch (error) { | |
| return { data: null, error: error as E }; | |
| } | |
| } |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Love the approach, but I think T3’s solution has a couple of type-safety concerns:
nullvalues introduce ambiguity — If null is a valid return type for your promise, then both Success and Failure could havedata: null, which makes narrowing unreliable and weakens type safety.Here’s how I implemented it instead:
This approach avoids unsafe casts, uses a clear boolean discriminator for type narrowing, and properly treats errors as unknown — the most type-safe way to handle thrown values in TypeScript.
Your application code then is required to do type guards / narrowing to properly type the error: