ethers@5.0.24 dependencies are resolved to the most recent ones due to ^ selector

[jbargu]

We are using ethers@5.0.24 for our library to have ethers interface to our own chain (non-Ethereum). For this purpose we inherit the Signer from @ethersproject/abstract-signer and Provider from @ethersproject/abstract-provider packages respectively. While the ethers@5.0.24 uniquely defines the dependencies version, those depedencies in turn, such as @ethersproject/abstract-provider@5.0.9 define them with ^ selector (for example "@ethersproject/bytes": "^5.0.4"). This means it pulls in the most recent release, e.g. @ethersproject/abstract-provider@npm:5.4.1. This package release however is not backward compatible with our code, since it uses different structure (at the moment there is a problem with non-existent getFeeData() among others).

Right now the only solution that works is pinning all the releases in the resolutions field within package.json to the ones in ethers@5.0.24 in our library and all the applications that uses our own library. This is a bit cumbersome and we would like to hide this from the user of the library. Do you see any better alternatives on how to remedy this issue?