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

Dependency minimalism (writing software that deliberately tries to have as few dependencies as practical) is a really underrated virtue imo.

Every single dependency is a risk that "something will go wrong" during someone's installation process. Installing projects with hundreds of dependencies and walking through errors can be incredibly frustrating.

https://farcaster.xyz/vitalik.eth/0xddf30244

https://npmgraph.js.org/?q=%40privy-io%2Freact-auth#zoom=h&color=moduleType

Barcelona based developer. I enjoy comics, gaming and sci-fi

Stripe bought privy based on its node_modules folder weight. Lesson in there

🐵 ← 🙈🙉🙊 → /phil →  phil.cockfield.net, db.team →  
ƒ(🌳) →  🧫 /sys  ←  @cell <T> 🧠🐦‍⬛, 100% human cartoon, waiheke

One of the biggest impediments to FC "clients" not taking off as a programming substrate in earlier times, I think can be attributed to just what a shit-show the underlying bramble of libraries required make this work is.  

It's hard though - unwinding an unwieldy large dependency graph is not easy feat.  Can't the whole thing be done with one instance of Viem? (I say, intentionally naively)

Yes yes yes. Please!

Adding the “crypto web3” stack in general, and all the 10K things that get willy-nilly dragged along with it is a real smell - not to mention the attach surface on all that.

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

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

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

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

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

Amusement, wonder, and uncertainty. now [redacted], prev @neynar ✴︎ libred.org

I don’t work at privy. Though we do integrate privy a lot in client projects at the boutique

It’s sad that appkit is such a bloated package :( Wish they would put more care in that regard (also making features optional and only load on demand)

Probably not a bot 🤷‍♂️ https://mulf.wtf

npx expo install expo-apple-authentication expo-application expo-crypto expo-linking expo-secure-store expo-web-browser react-native-passkeys react-native-webview @privy-io/expo-native-extensions @privy-io/expo

its absolutely a mess. I was working on a RN app and was integrating privy and it was an actual nightmare. AND they gatekeep conditional transfers behind their "rules engine" for enterprise. But they just got acquired for a fat stack, so what do i know?