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 🙏

T3Dotgg's resource offers insights, tutorials, and resources for gamers and esports enthusiasts. Readers can learn about gaming news, esports events, and professional gaming strategies. With articles, reviews, and interviews, T3Dotgg provides  guidance and expertise for staying informed and competitive in the world of gaming.

Theo - t3․gg

The author discusses the challenges and solutions for handling errors in TypeScript projects, emphasizing the limitations of traditional try-catch blocks. The piece introduces a custom try-catch function that simplifies error handling and explores other advanced libraries like neverthrow and effect, highlighting their benefits and complexities. The author shares insights and recommendations for developers to manage errors more effectively in their codebases.

I put this function in every codebase

I have my own utility that does this, as well. I call it like this:
<pre><code class="language-typesript">const [data, error] = await assert(somePromise());
</code></pre>
Same idea, different name.

Honestly reminds me of callbacks, before async/await were a thing…
<pre><code class="language-javascript">function myFunc (cb) {
 try {
 // Do stuff
 return cb(null, /* data */{})
 } catch (err) {
 return cb(err)
 }
}

myFunc((err, data) =&gt; {
 if (err) { 
 console.log(err)
 return
 }
 // No error was passed, proceed with doing stuff..
})
</code></pre>

Great!
If you intend to use this tryCatch() globally, I would also suggest passing in a context. It might be a bit heavy handed, but super handy.