Skip to content


Wake comes with default compilation settings that should work for many projects. However, in some cases, it may be necessary to customize the compilation settings.

To run the compiler, use:

wake compile

The --help flag can be used to display additional options.


Wake comes with wake init (to initialize a new or existing project) and wake init config (to prepare just the wake.toml config file) commands. The commands can automatically set remappings for Foundry projects and enable the solc optimizer if needed.

Include paths#

Include paths define locations where to search for Solidity files imported using direct (non-relative) import strings. An example of a direct import string is:

import "openzeppelin/contracts/token/ERC20/ERC20.sol";

The default settings for include paths are:

include_paths = ["node_modules"]


Include paths should only be used if path segments (directories in the import string) reflect directories in the file system.

For example, if the import string is import "openzeppelin/contracts/token/ERC20/ERC20.sol";, but the file is located at node_modules/openzeppelin/src/contracts/token/ERC20/ERC20.sol, then include paths cannot be used because of the src directory in the path.


Remappings allow performing a substitution in import strings. More information about remappings can be found in the Solidity documentation.


It is highly recommended to use include paths instead of remappings whenever possible.

Foundry projects#

Include paths typically cannot be used in Foundry projects. The forge remappings command can generate remappings that can be copied into the wake.toml file:

$ forge remappings

remappings = [

Exclude paths#

Exclude paths define locations of Solidity files that should not be compiled unless imported from another non-excluded file.

The default settings for exclude paths are:

exclude_paths = ["node_modules", "venv", ".venv", "lib", "script", "test"]

Via IR#

The compiler can can generate bytecode by converting the sources to Yul first (Solidity -> Yul -> EVM bytecode) instead of the traditional Solidity -> EVM bytecode approach. See the Solidity documentation for more information.

By default, the via_IR config option is left unset, which leaves the decision to the compiler. It can be enabled by setting the option to true:

via_IR = true

Stack too deep errors

One way to avoid Stack too deep errors is to enable via_IR and the optimizer.


Wake allows setting all optimizer options supported by the Solidity compiler (see the Solidity documentation). By default, Wake leaves the enabled option unset, which leaves the decision to the compiler. It can be enabled by setting the option to true:

enabled = true
runs = 200