-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove web3-react dependency #409
Comments
I'd be all for this as web3-react seems to not be updated very frequently and troubleshooting issues with useDapp is quite an exercise on determining if the problem is here, there, or all the way in ethers. useDapp has been an amazing library. I thank you for your efforts on it. |
Yeah web3-react seems to not be actively maintained. The Ledger connector is using deprecated U2F browser API, so direct Ledger support is currently not possible with useDapp while web3-react is a dependency. This kind of issue is likely to get worse and worse very quickly as that repo becomes stale.. |
I think this issue can be closed now 🌈 |
It feels like it is time to remove web3-react and create own state machine to manage connection state.
Motivation
(related An "official" example of using useDapp with "Web3Modal" in the useDapp docs would increase adoption a lot #345, Improve Docs of useEthers hook #332, Provide
useRPC
hook to allow dynamic change of RPC provider #282, WalletConnect integration - any idea guys? #292)Implementation proposal
Only one (or zero) network can be active for writing while multiple networks can be active for reading.
Use
activate(provider)
to switch active networks.Configuration
New configuration format:
Error handling
Returns an array of typed errors
ConnectionError[]
, related to connection.Errors will disappear once the reason is not valid anymore (e.g. activation failed is cleared by the next successful activations)
The text was updated successfully, but these errors were encountered: