Web3 & DApp Development Fundamentals · Lesson

Compiling Contracts

Build artifacts.

Compiling Contracts is a free Web3 & DApp Development Fundamentals lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Web3 & DApp Development Fundamentals learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Why Compile

Solidity source code cannot run on the EVM directly. The compiler turns .sol files into bytecode and an ABI that tools and clients use.

Bytecode — the low-level instructions deployed on-chain.
ABI — a JSON interface describing functions and events.

The Compile Task

Hardhat compiles every contract under contracts/ with a single command:

npx hardhat compile

Hardhat downloads the right solc version automatically, so you do not need to install the compiler manually.

npx hardhat compile

Choosing the Solidity Version

The compiler version is set in hardhat.config.js and must satisfy the pragma in your contracts:

module.exports = {
  solidity: "0.8.24",
};

If your contract says pragma solidity ^0.8.24;, the configured version must be compatible or compilation fails.

module.exports = {
  solidity: "0.8.24",
};

Build Artifacts

After compiling, Hardhat writes output to the artifacts/ folder. Each contract gets a JSON file containing:

abi — the application binary interface.
bytecode — deployment bytecode.
deployedBytecode — runtime bytecode.

These artifacts are what ethers.js loads to interact with your contract.

The Cache Folder

Hardhat keeps a cache/ folder to track what changed. On the next compile, only modified files are recompiled.

This incremental compilation makes large projects build quickly. If something seems stale, you can force a fresh build.

Cleaning the Build

To remove cached and generated files, run the clean task:

npx hardhat clean

This deletes artifacts/ and cache/. Use it when you suspect a stale artifact is causing odd behavior, then recompile.

npx hardhat clean

Compiler Optimizer

The optimizer reduces gas costs and bytecode size. Enable it in the config:

module.exports = {
  solidity: {
    version: "0.8.24",
    settings: {
      optimizer: { enabled: true, runs: 200 },
    },
  },
};

A higher runs value optimizes for frequent calls; a lower value optimizes for deployment size.

module.exports = {
  solidity: {
    version: "0.8.24",
    settings: {
      optimizer: { enabled: true, runs: 200 },
    },
  },
};

Multiple Compiler Versions

If different contracts need different Solidity versions, list several compilers:

module.exports = {
  solidity: {
    compilers: [
      { version: "0.8.24" },
      { version: "0.7.6" },
    ],
  },
};

Hardhat picks a matching compiler for each file based on its pragma.

module.exports = {
  solidity: {
    compilers: [
      { version: "0.8.24" },
      { version: "0.7.6" },
    ],
  },
};

Reading Compiler Warnings

The compiler reports errors (which stop the build) and warnings (which do not). Common warnings include:

Unused local variables.
Shadowed declarations.
Functions that could be marked view or pure.

Treat warnings seriously — they often hint at real bugs.

Using the ABI Later

Once compiled, you import the artifact in scripts or tests to attach to a contract:

const artifact = require("./artifacts/contracts/Greeter.sol/Greeter.json");
console.log(artifact.abi);

Tools like ethers.js use this ABI to encode and decode calls correctly.

const artifact = require("./artifacts/contracts/Greeter.sol/Greeter.json");
console.log(artifact.abi);

Forcing a Recompile

By default Hardhat skips files that have not changed. To rebuild everything without cleaning, pass the force flag:

npx hardhat compile --force

This is useful after changing compiler settings, which the incremental cache may not detect on its own.

npx hardhat compile --force

Quick Check

Test your understanding of compilation in Hardhat.

Recap

You learned how Hardhat compiles contracts.

npx hardhat compile builds all contracts and downloads the right solc.
Artifacts (ABI + bytecode) land in artifacts/; incremental builds use cache/.
npx hardhat clean removes stale output.
The optimizer and multiple compiler versions are configured in hardhat.config.js.
Always fix warnings — they often reveal bugs.

Frequently asked questions

Is the “Compiling Contracts” lesson free?

Yes — the full text of “Compiling Contracts” is free to read here on the web, and the Web3 & DApp Development Fundamentals course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Web3 & DApp Development Fundamentals course, upgrade to CoddyKit PRO.

What will I learn in “Compiling Contracts”?

Build artifacts. You practise Web3 & DApp Development Fundamentals with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Web3 & DApp Development Fundamentals?

No prior experience is required. Web3 & DApp Development Fundamentals on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Compiling Contracts” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Web3 & DApp Development Fundamentals lesson?

Yes. Every Web3 & DApp Development Fundamentals lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Web3 & DApp Development Fundamentals