Seonglae ChoError handling system
Throw in Library layer and Catch in Application layer
Minimize cases where exceptions are simply returned to improve debugging
- Criteria for distinguishing between expected and unexpected errors
- Tools for error monitoring
- Mechanisms to prevent error propagation
Choose approaches that are intuitive and reusable in the given context, rather than focusing on declarative vs imperative
Error Handlings
Error Handling Services
neverthrow
supermacro • Updated 2026 Mar 23 14:43
proposal-try-operator
arthurfiorette • Updated 2026 Mar 20 9:8
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
Failures, Mistakes, Confusion
I feel like there's quite a bit of confusion online in discussions of different "error handling
models" in programming,
and I think that it's probably because basically every "error handling model" in programming
languages I've seen conflates
two (or more!) separate concepts into a single system.
https://blog.ignaskiela.eu/failures-mistakes-confusion.html
React에서 선언적으로 비동기 다루기
에러를 효율적으로 다루기 위해 선언적으로 에러를 정의하고 처리하는 방법을 고민했고 그 결과물을 공유합니다. Suspense와 ErrorBoundary 를 사용하여 비동기 컴포넌트를 보다 효율적으로 처리하는 컴포넌트를 소개합니다. 우리에게 익숙한 명령형으로 비동기 처리와 에러 처리하는 부분에 대해 먼저 살펴보려고 한다. 먼저 일반적인 비동기 처리를 살펴보자. 이런 간단한 호출의 경우에도 비동기 상태에 따른 별도 처리가 필요하다.
https://jbee.io/react/error-declarative-handling-1/
