Farcaster Devs

Viem

viem’s extreme type safety is awesome if you know the exact shape of all your parameters the moment you call each client action.

As soon as you want to derive your own composable helper functions with partial or variable parameters… the TypeScript generics get complicated, fast. 😅

So I was upgrading Hubble to @viem v2.0, and some wrapper class instances were giving *super gnarly* deeply-nested TypeScript errors in some unexpected places.

Of course, viem's internal conditional types run so deep that it's impossible to interpret the root cause of the mismatch just by looking at one of these 🤪

TypeScript Interface for Ethereum ~ viem.sh

/frontend dev (HTML/CSS)・founder/decentralized data wrangler /blockhead・contributor /ethglobal /walletbeat・hackathon bounty hunter・music maker・dropout・nomad・25

the massive object to object comparison with one slightly different attribute, that has its own deeply nested structure has bit me in the past 

viem is great but once you go slightly off the beaten path it gets murky real quick

typescript

At this point VSCode should just have a built-in stack tracer solely dedicated to TypeScript's generic type functions 🤔

Yeah, I’d say it’s a glaring weakness in the current state of TypeScript tooling more than anything.

It just can’t keep up with the sheer wizardry of @awkweb and @jxom 😉

Yeah, I’d say it’s a glaring weakness in the current state of TypeScript tooling more than anything.

It just can’t keep up with the sheer wizardry of @awkweb and @jxom 😉 

https://warpcast.com/darrylyeo/0x7b315658