devFC

Not writing API's in effect-ts means error handling is such a pain. WHYYYYYYY

I get tired of try{} catch {} blocks around everything and then doing the same on the frontend.

make errors first class citizens. Handle it properly and enjoy end to end type safety (errors are types too)

thanks.

Farcaster Product Studio @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

too bad this isn’t at the language level

unrealistic for libraries to all add an opinionated library as dep

Building @warpcast and @farcaster, new dad, like making food

the wevm team does a nice job of exposing types for errors thrown per function, I've started following this in frame-sdk

a wrapper to lifts this into effect could be a nice supplemental library

I understand that though it works well enough at an app level to run a library in an effect though that obviously doesn’t give the error handling right away or the library error that may come up