Different WalletClient objects between wagmi and viem

[70nyIT]

I'm creating an SDK plugin that has hooks accepting a WalletClient object to be used with viem library methods.

The plugin is intended to be used in react applications using wagmi, similarly to

const {data: walletClient} = useWalletClient();
const myHook = useHook(walletClient, otherData);

Since wagmi and viem are very interconnected I was expect that the viem WalletClient object to be the same as wagmi WalletClient object. Instead I noticed that they're different, causing an error when using the hook.

Specifically, the value account in wagmi is always of type Account, while in viem is Account | undefined. Is this intended or should be reported as a bug? And if it's intended, why it's different with the same name? Any suggestion on how to correctly use it?

My idea is to import types of wagm in my SDK plugin ad mention that I want to accept a wagmi WalletClient object, still not sure if this will bring other incompatibility. My suggestion would be to keep the same types between wagmi and viem.

[70nyIT]

I'd like t bump it to see if there's anyone that encountered this error, or if a workaround can be found. I feel that the two WalletClient objects should be the same, or at least having different names.

[AlphaDio]

Why has this not been answered?

[AlphaDio]

const walletClient = getConnectorClient(config)

Hope it helps.

[70nyIT]

unfortunately the problem is at TypeScript level, where two objects diff for that optional account parameter

[AlphaDio]

Yeah, I ended up having to scrap the whole using walletClient for getContract.