privy

walletconnect

Looks like the current latest version of @reown AppKit comes with two different versions of @viem, and in turn FOUR different versions of two libraries from @paulm’s Noble Cryptography suite.

Fun stuff.

TIL @privy’s `@privy-io/react-auth` package straight up depends on @reown AppKit.

That’s... a LOT of node_modules 😵

Would like to see this slimmed down significantly. Dependency minimalism, pretty please.

The easiest way to bring all your users onchain, regardless of whether they already have wallets | Customer love at privy.io/love

Toolkits to build onchain UX → /reown. Builders of the WalletConnect Network. For the WalletConnect Network, please visit @walletconnect

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

Curious what they're using reown for but I would guess something related to walletconnect. WC is practically a must-have and isn't very easy to connect to yourself

Hadn’t looked at the @reown / @walletconnect ecosystem in a bit and got pretty confused by all the different packages they have to offer.

Ended up generating some diagrams on npmgraph to tease out what depends on what 😅

Interested in this myself. Would love for @walletconnect to clarify in their docs how to best make use of the underlying core packages.

cc @pedrouid

Interested in this myself. Would love for @walletconnect to clarify in their docs how to best make use of the underlying core packages.

cc @pedrouid

https://farcaster.xyz/darrylyeo/0x20bc400a

This is great. Will have to dive deeper into this.

If you're curious: https://github.com/thirdweb-dev/js/tree/main/packages/thirdweb/src/wallets/wallet-connect/receiver

I've done it with just their lower level packages but I definitely had to go digging. They push the AppKit stuff pretty hard in their docs and this was a year ago before reown was a thing