Joshua Hyde (he/him)
@jrh3k5.eth
web3 frontend dev is maddening. Spend yesterday and this morning learning to build a vanilla wagmi React app. Got it working, so I started looking at making it pretty. However, if I want to use something like RainbowKit in it, it completely breaks the entire app and none of the steps in the RainbowKit guide line up with how wagmi sets up the project. It's as if there's an assumption that you'll only ever start from scratch with these modules and, if you don't, you'd better just start over, I guess? The aggressive component lock-in and lack of modular design is truly frustrating.
2 replies
0 recast
2 reactions
Daniel Sinclair
@danielsinclair
Can try to improve this for RainbowKit! What did your setup look like that had you stuck? Mind sharing some sample code/repo?
1 reply
0 recast
0 reaction
Joshua Hyde (he/him)
@jrh3k5.eth
This is the repo: https://github.com/jrh3k5/ploan-react/ (be gentle, it's my first React project) I created it as a starter wagmi project per their doc and tried to run through the manual installation here: https://www.rainbowkit.com/docs/installation#manual-setup What was frustrating was how the code referenced in there didn't seem to really line up nicely with what the wagmi template had generated. As someone brand new to React and wagmi - and exploring it in my free time - it was one of those things where I eventually landed on, "RainbowKit is prettier, but vanilla wagmi works and I want to focus on other things in this project," so I opted to abandon RainbowKit integration.
0 reply
0 recast
0 reaction
