rainbowkit
rainbowkit copied to clipboard
rainbow-me
feat: add Exodus Wallet
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated |
|---|---|---|---|---|
| rainbowkit-example | ✅ Ready (Inspect) | Visit Preview | 💬 Add your feedback | Jan 27, 2023 at 1:26PM (UTC) |
| rainbowkit-site | ✅ Ready (Inspect) | Visit Preview | 💬 Add your feedback | Jan 27, 2023 at 1:26PM (UTC) |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thanks for the contribution here @gutenye – we're currently discussing out strategy for adding new wallets to the repo and how we can best serve the RainbowKit community while also not being gatekeepers/maintainers of every wallet integration. I'll let you know when we have an update! Thanks for your patience!
Sorry for the delay on this, and thanks for the PR!
We've just re-worked RainbowKit internals in v0.7 so that wallets can be imported individually, ensuring our bundle size doesn't keep increasing as we continue to add more wallets.
Are you able to give us write access to your fork so that we can get you updated to the new API and apply some changes before merging? Alternatively, I've already made the updates in a branch if you'd like to replay them manually yourself: https://github.com/rainbow-me/rainbowkit/tree/%40markdalgleish/exodus-pr-updates
@bulgakovk is attempting to deploy a commit to the rainbowdotme Team on Vercel.
A member of the Team first needs to authorize it.
Hey there! Just rebased the PR again, please lemme know if there's something else missing
Deployment failed with the following error:
Was unable to schedule a deployment.
@DanielSinclair Anything else we can do to help you guys getting this across the line?
Seeing a few performance issues on our example dApp deployment here: https://rainbowkit-example-4jvxs45am-rainbowdotme.vercel.app/ When refreshing, the injected connector is not always detected; this pushes users to the install flow and prevents auto reconnect on dApps they've already interacted with. The likely cause is a race condition between RainbowKit initialization and the extension performing additional work before injecting the connector.
Closing for now, but will revisit and reopen if this connector begins working as expected