Try Catch Block

Readability is significantly reduced

Feels like using GOTO statements due to being disconnected from the main code flow

This can lead to duplicate exception handling and difficult maintenance

Ruins the
Static Typing

Go style is better


export async function trycatch<T, E = Error>(
  promise: Promis<T>,  
): Promise<Result<T, E>> {
  try {
    const dta = await promise;
    return { data, error: null }
  } catch (error) {
	  return { data: null, error: error as E }
  }
}

neverthrow

supermacro • Updated 2026 Mar 23 14:43

proposal-try-operator

arthurfiorette • Updated 2026 Mar 20 9:8

Effect ts

The most important function in my codebase

Error handling in TypeScript is bad. Try catch is NOT a good pattern. Go got a lot wrong, but returning errors as values was absolutely right. Thank you CodeRabbit for sponsoring! Check them out at: https://soydev.link/coderabbit SOURCES https://gist.github.com/t3dotgg/a486c4ae66d32bf17c09c73609dacc5b https://github.com/supermacro/neverthrow https://effect.website/ https://ethanniser.dev/blog/the-truth-about-effect/ Try T3 Chat? https://soydev.link/chat Want to sponsor a video? Learn more here: https://soydev.link/sponsor-me Check out my Twitch, Twitter, Discord more at https://t3.gg S/O Ph4se0n3 for the awesome edit 🙏

https://www.youtube.com/watch?v=Y6jT-IkV0VM

간단한 모나드 설명과 예제

https://black7375.tistory.com/69

Try Catch Block

Go style is better

Recommendations