Hardhat Project Setup & Configuration
Hardhat is the most popular Ethereum development framework. It provides a local blockchain, TypeScript-based test runner, deployment scripts, and a rich plugin ecosystem.
Hardhat Project Structure
Standard Hardhat project layout:
my-project/
contracts/ - Solidity source files
scripts/ - Deployment and utility scripts
test/ - Test files (TypeScript)
ignition/ - Hardhat Ignition deployment modules (v2)
artifacts/ - Compiled ABIs and bytecode (auto-generated)
cache/ - Compilation cache (auto-generated)
hardhat.config.ts - Main configuration file
.env - Secrets (NEVER commit to git)
.gitignore - Must include: node_modules, artifacts, cache, .env
Key packages:
- hardhat - core framework
- @nomicfoundation/hardhat-toolbox - includes ethers.js, chai, mocha, hardhat-network-helpers, hardhat-etherscan, coverage, gas-reporter
- dotenv - load .env variablesCommon Mistakes
- Committing .env to git - add .env to .gitignore immediately. GitHub secret scanning will flag it but the damage may already be done.
- Not pinning the Solidity version - always use 0.8.x exact version in hardhat.config.ts for reproducible builds. Different compiler versions produce different bytecode.
- Using the wrong network accidentally - always double-check the --network flag. Deploying to mainnet when intending Sepolia costs real ETH.
Tip
Tip
Practice Hardhat Project Setup Configuration in small, isolated examples before integrating into larger projects. Breaking concepts into small experiments builds genuine understanding faster than reading alone.
Once deployed, smart contracts are immutable - code is law
Practice Task
Note
Practice Task - (1) Write a working example of Hardhat Project Setup Configuration from scratch without looking at notes. (2) Modify it to handle an edge case (empty input, null value, or error state). (3) Share your solution in the Priygop community for feedback.
Quick Quiz
Common Mistake
Warning
A common mistake with Hardhat Project Setup Configuration is skipping edge case testing - empty inputs, null values, and unexpected data types. Always validate boundary conditions to write robust, production-ready web3 code.
Key Takeaways
- Hardhat is the most popular Ethereum development framework.
- Committing .env to git - add .env to .gitignore immediately. GitHub secret scanning will flag it but the damage may already be done.
- Not pinning the Solidity version - always use 0.8.x exact version in hardhat.config.ts for reproducible builds. Different compiler versions produce different bytecode.
- Using the wrong network accidentally - always double-check the --network flag. Deploying to mainnet when intending Sepolia costs real ETH.