Hardhat project structure and compilation config — Forge College

Struggling with mismatched Solidity compiler versions or strange gas behavior after compiling? Understanding how Hardhat maps your project files to compilation settings prevents costly runtime surprises and wasted debugging time.

What you'll learn
In this lesson you'll get a practical, block-by-block walkthrough of hardhat.config.js (or hardhat.config.ts) with a focus on Solidity compilation. You'll learn how Hardhat chooses a compiler from a compilers array or a single version string, and how pragma statements and explicit overrides influence selection. We explain optimizer settings (enabled and runs), metadata options like bytecodeHash, and why those choices change bytecode and gas profiles. You'll also learn where Hardhat places artifacts and cache, how to change paths in the config, and how to apply per-contract compiler overrides to compile a specific contract with its own version and optimizer settings.

Who this is for
This lesson is aimed at intermediate Ethereum developers who know basic Solidity and npm/TypeScript project layouts and want to reliably control compilation behavior across a project.

Key topics covered
- Anatomy of hardhat.config.js / hardhat.config.ts: solidity, compilers, settings, overrides
- Compiler selection mechanics: version vs compilers array and pragma resolution
- Solidity optimizer: enabled flag, runs parameter, and gas implications
- Per-contract overrides: configuring a legacy contract with a different compiler
- Paths and outputs: artifacts, cache, sources, and tests location
- Practical exercise: change config to compile one contract with a specified version and verify outputs

Ready to apply these patterns in your projects? Explore more guides and enroll in structured lessons at https://www.forge.college/

Видео Hardhat project structure and compilation config — Forge College канала Forge College