Document ethers 4 and 5 Web3Provider incompatibility. #1940
Unanswered
eccentricexit
asked this question in
Q&A
Replies: 1 comment 1 reply
-
One of the main reasons we have major version changes is to allow us to break backwards-compatibility. It is not common to be able to use objects from one major version in another. This should not be surprising. :s It depends a lot on what you are trying to do, but if you must, you could always wrap the provider in a Eip1193Bridge from v4 and then use the Web3Provider in v5 to wrap that. It is clunky, but might hold you over until the upstream dependencies catch up. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem: web3-react project using ethers 4 cannot use a library depending on ethers 5 because the two versions of Web3Provider are incompatible.
Document this or provide a path to use an ethers 4 provider on ethers 5 so users don't have any surprises.
Beta Was this translation helpful? Give feedback.
All reactions