hardhat icon indicating copy to clipboard operation
hardhat copied to clipboard

Hardhat is a development environment to compile, deploy, test, and debug your Ethereum software.

Results 780 hardhat issues
Sort by recently updated
recently updated
newest added

Review reporter flushing procedure if needed: * https://github.com/NomicFoundation/hardhat/pull/6225#discussion_r1943663103

status:ready
v-next

Since the EDR accounts are not real, it may not be necessary to use config variables, which would simplify the provider code.

status:ready
v-next

Remove the `enableRip7212` and `enableTransientStorage` fields from the EDR network config, as these were introduced for specific needs in the past and are no longer required. Additionally, remove all related...

status:ready
v-next

Current behavior: `initialBaseFeePerGas` is validated based on the `hardfork`, but this validation should apply only to `l1` chain types. Expected behavior: `initialBaseFeePerGas` should be validated based on both the `hardfork`...

status:ready
v-next

Current behavior: the `hardfork` value in the user config is validated by Zod as a value in the `HardforkName` enum. However, this validation is only appropriate for the `l1` chain...

status:ready
v-next

The loading of compilation artifacts into the running EDR instance needs to be revisited for Solidity Test. We will be looking at compilation artifact loading for stack trace support, the...

status:ready
v-next

In Hardhat 3 Solidity Tests we only print `console.logs` if there has been a test failure. The feedback from users is this is unexpected. We should switch this to the...

status:ready
v-next

This one was raised by Franco: > The detection of the package manager is wrong when doing `pnpm dlx @ignored/hardhat-vnext@next --init`. It installs things with npm. My guess is that...

status:ready
v-next

This needs to designed out. In Hardhat 2 stack trace metadata can only be passed between Hardhat and and in-memory EDR instance. In Hardhat 3 we want to support stack...

status:needs-priority

### Version of Hardhat 3.0.0-next.4 ### What happened? The Hardhat node test runner outputs meaningless information on some failing tests. Two examples: 1. (edit: this issue has been fixed) `assert.match`...

status:ready
v-next