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

@v, you wanted more context on the `@ts-ignore`…

This was the context 😂

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

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

Anyway, after several hours I eventually figured out the right type parameters to add in order to satisfy the system 😮‍💨

I definitely have a better grasp on managing type parameters now. Basically, keep defaults as broad as possible, if not the same as the constraint.

Takes discipline, but if you do it right you won't be tempted to duplicate parameters all the way up the dependency tree (like I almost did here for `Hub` / `SyncEngine`):

Here's the commit in case you were curious @awkweb @jxom:

Here's the commit in case you were curious @awkweb @jxom:

https://github.com/farcasterxyz/hub-monorepo/pull/2181/commits/9fcb2a23f4172e02890f9cee91c5df72faa73e29

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

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

what a G!

Maybe this would be helpful next time!

I do have this installed, but the popup window that appears when I hover over the error is so small I have to scroll at least 10 pages to get to it 😅

The error message itself also just isn’t particularly helpful in this case

what a G!

Maybe this would be helpful next time!
https://github.com/yoavbls/pretty-ts-errors

geez, the error is larger than the average ts codebase