We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
brownie
hardhat
solc
I'm testing out swapping ganache-cli for hardhat@dtt on the argobytes repo.
I then ran brownie test --network mainnet-fork, but it fails because it tries to use this command:
brownie test --network mainnet-fork
Launching 'hardhat node --fork https://yournode --port 8575 --chainId 1 --hardfork istanbul'...
Neither --chainId, nor --hardfork are flags in hardhat. You can set them, but instead of with flags, they are set in hardhat.config.js
hardhat.config.js
In a separate terminal, run hardhat node --fork https://yournode
hardhat node --fork https://yournode
Either don't pass these flags, or add them to hardhat.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Environment information
brownie
Version: 48d3f18hardhat
Version: 2.1.3-dtt.0 sha512-QWI3LbImf5vyshQzC2nGxzkgtMHsK5BovcWUMgNl3f/0QGCtVRLhTvkA6/FK0f8XhDkFCOHLsJmyRrt4Ao9grg==solc
Version: 0.8.3What was wrong?
I'm testing out swapping ganache-cli for hardhat@dtt on the argobytes repo.
I then ran
brownie test --network mainnet-fork
, but it fails because it tries to use this command:Neither --chainId, nor --hardfork are flags in hardhat. You can set them, but instead of with flags, they are set in
hardhat.config.js
Workaround
In a separate terminal, run
hardhat node --fork https://yournode
How can it be fixed?
Either don't pass these flags, or add them to hardhat.
The text was updated successfully, but these errors were encountered: