Last active
June 6, 2025 03:30
-
Star
(738)
You must be signed in to star a gist -
Fork
(118)
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 }; | |
} | |
} |
i made a npm package which is basically just theo's version but with added support for sync functions
npmjs.com/package/typecatchThis would work better if it returned undefined on error, so you could use a default value shorthand when spreading an object.
![]()
update to 0.2.2 :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Impossible, since you can only know that at runtime.