// the take
Hardhat is the dominant JavaScript/TypeScript-based Ethereum smart contract development environment, handling compilation, testing, debugging, and deployment. The repo is currently mid-transition to v3, which is a significant architectural rewrite. It's aimed at Solidity developers who want to stay in the Node.js ecosystem rather than moving to Foundry.
- The plugin ecosystem and ethers.js/viem integration are mature and battle-tested across thousands of production projects — the chai matchers for revert reasons, event assertions, and balance changes are genuinely useful and hard to replicate manually.
- Hardhat Network (the built-in EVM) supports mainnet forking, console.log in Solidity, and stack traces with source mapping — the debugging experience is meaningfully better than raw ganache ever was.
- The monorepo structure is well-organized with proper changesets, per-package changelogs, and a real CI pipeline including regression benchmarks against real-world projects like Aave, Uniswap, and OpenZeppelin.
- v3 introduces native Solidity test support alongside Mocha, which reduces the friction of maintaining two separate test suites that Foundry shops currently deal with.
- v3 is still in flux and not yet the stable release — the README points here but the previous v2 branch is what most existing projects run, creating documentation confusion for anyone starting fresh today.
- Test execution speed is a known weak point compared to Foundry's native Rust EVM; for large test suites this isn't a minor inconvenience, it's a build pipeline bottleneck that has driven meaningful ecosystem migration.
- The plugin API has historically been weakly typed and prone to breaking when core internals change; v3 is apparently redesigning this, but existing plugin authors are stuck maintaining two major versions.
- No built-in fuzzing or formal verification integration — you still need to bolt on external tools, whereas Foundry ships with fuzz testing out of the box, which is now table stakes for serious contract security work.
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →