Right now this is causing quite a lot of frustrating problems for us. Because this package has a dependency on ethers v4, and then an aliased dependency on ethers v5, sometimes an npm/yarn install will get completely confused about which version is which and our app (running on v5) will attempt to use the v4 version used by this package.
I'll paste a snippet from my yarn.lock where you can see that all other dependents of ethers are being redirected to your ethersv5 alias:
Right now this is causing quite a lot of frustrating problems for us. Because this package has a dependency on ethers v4, and then an aliased dependency on ethers v5, sometimes an npm/yarn install will get completely confused about which version is which and our app (running on v5) will attempt to use the v4 version used by this package.
I'll paste a snippet from my yarn.lock where you can see that all other dependents of ethers are being redirected to your
ethersv5
alias:The problem is (I think) that webpack/next/etc. don't know to load ethers from the aliased folder, so they just pull the v4 version!
Is there a reason why v4 is still a dependency (and a top-level dependency) and you haven't upgraded?