Closed ashwinYardi closed 9 months ago
One more example:
The error is the same. AbstractProvider from ethers lib inside ethers-multicall-provider and AbstractProvider driectly imported from ethers clash with each other. :(
Can you ref a repository pls? Every time i had this error there were 2 versions of ethers installed at the same time. I need to check your lock file
Hey will quickly spin up a project and share the similar setup with you.
Hey, so I was not getting this error in the new project that I had setup. So after your hint that this could be due to dependency issues, I cleaned the cache, deleted the lock file, reinstalled ethers and ethers-multicall-provider andd BAMM, the type erros are gone.
Not sure, what was causing the issue, but for now got it working. Thank you so much!
Great! Hopefully it'll be helpful to others later!
Current Behavior
As shown in the above image, in both the cases, when trying to wrap AbstractProvider, the type error is shown:
So apparently, two different variations of the type AbstractProvider are being used which is causing the collision.
AbstractProvider returned by
getDefaultProvider
in ethers v6 is different that what is epected byethers-multicall-provider
Environment