Closed samlaf closed 1 year ago
This is a dupliacte of https://github.com/wighawag/hardhat-deploy-ethers/issues/12
There are some other work around mentioned there, including using npm aliases
It might also be a good idea to tell tenderly team to not hardcode dependency on other plugin so user can chose to use different implementation
hardhat-deploy-ethers aims at becoming an extension of hardhat-ethers but unfortunately there is a blocking issue : https://github.com/NomicFoundation/hardhat/issues/1040
You can see in my package.json that I already have "@nomiclabs/hardhat-ethers": "npm:hardhat-deploy-ethers@^0.3.0-beta.10"
hardhat-ethers installed as an alias. I even tried removing the carret "^" as you suggested in one of the related issues, but nothing works. removed node_modules and yarn.lock and reinstalled; still same issue.
I will open an issue in hardhat-tenderly. How can they fix this? How should they go about installing hardhat-ethers without hardcoding it, as you suggest?
hardhat-ethers without hardcoding it, as you suggest?
they can import it at runtime if needed, but they might not even need it in the first place. hardhat-deploy-ethers depends o hardhat-deploy yet do not have a hardcoded dependency on hardhat-deploy, it simply uses it and so tell user to install it.
hardhat-deploy-ethers@next has been released Please, try it out.
It is now an extension to hardhat-ethers so you need both
But note that that new version do not support external artifact if you were using them
There are a few similar issues already, like https://github.com/wighawag/hardhat-deploy-ethers/issues/1 and https://github.com/wighawag/hardhat-deploy-ethers/issues/12, but none that mention tenderly-cli.
my
ethers.getContract
function was working fine, until I installed hardhat-tenderly. Now, I get errors.When I import hardhat-tenderly before hardhat-deploy-ethers in hardhat.config.ts,
I get (but adding a
// @ts-ignore
the code runs fine, so its just a ts module problem..)If I change the ordering in hardhat.config.ts,
and this time even adding
// @ts-ignore
does not fix the issue.Any idea what is going on? My package.json looks like