12 stable releases

✓ Uses Rust 2018 edition

new 1.0.11 May 28, 2020
1.0.10 May 7, 2020
1.0.9 Jan 20, 2020
1.0.8 Oct 20, 2019
1.0.4 Jul 8, 2019

#10 in WebAssembly

Download history 793/week @ 2020-02-09 982/week @ 2020-02-16 1048/week @ 2020-02-23 734/week @ 2020-03-01 1067/week @ 2020-03-08 1066/week @ 2020-03-15 1124/week @ 2020-03-22 1122/week @ 2020-03-29 1183/week @ 2020-04-05 1272/week @ 2020-04-12 1404/week @ 2020-04-19 1466/week @ 2020-04-26 1575/week @ 2020-05-03 1619/week @ 2020-05-10 1444/week @ 2020-05-17 1660/week @ 2020-05-24

5,446 downloads per month


625 lines

Wasm builder is a utility for building a project as a Wasm binary

The Wasm builder is a tool that integrates the process of building the WASM binary of your project into the main cargo build process.

Project setup

A project that should be compiled as a Wasm binary needs to:

  1. Add a build.rs file.
  2. Add substrate-wasm-builder as dependency into build-dependencies.

The build.rs file needs to contain the following code:

use wasm_builder_runner::{build_current_project, WasmBuilderSource};

fn main() {
		// The name of the file being generated in out-dir.
		// How to include wasm-builder, in this case from crates.io.

As the final step, you need to add the following to your project:

include!(concat!(env!("OUT_DIR"), "/wasm_binary.rs"));

This will include the generated Wasm binary as two constants WASM_BINARY and WASM_BINARY_BLOATY. The former is a compact Wasm binary and the latter is not compacted.


Wasm builder supports to enable cargo features while building the Wasm binary. By default it will enable all features in the wasm build that are enabled for the native build except the default and std features. Besides that, wasm builder supports the special runtime-wasm feature. This runtime-wasm feature will be enabled by the wasm builder when it compiles the Wasm binary. If this feature is not present, it will not be enabled.

Environment variables

By using environment variables, you can configure which Wasm binaries are built and how:

  • SKIP_WASM_BUILD - Skips building any wasm binary. This is useful when only native should be recompiled.
  • BUILD_DUMMY_WASM_BINARY - Builds dummy wasm binaries. These dummy binaries are empty and useful for cargo check runs.
  • WASM_BUILD_TYPE - Sets the build type for building wasm binaries. Supported values are release or debug. By default the build type is equal to the build type used by the main build.
  • TRIGGER_WASM_BUILD - Can be set to trigger a wasm build. On subsequent calls the value of the variable needs to change. As wasm builder instructs cargo to watch for file changes this environment variable should only be required in certain circumstances.
  • WASM_BUILD_RUSTFLAGS - Extend RUSTFLAGS given to cargo build while building the wasm binary.
  • WASM_BUILD_NO_COLOR - Disable color output of the wasm build.
  • WASM_TARGET_DIRECTORY - Will copy any build wasm binary to the given directory. The path needs to be absolute.
  • WASM_BUILD_TOOLCHAIN - The toolchain that should be used to build the wasm binaries. The format needs to be the same as used by cargo, e.g. nightly-2020-02-20.

Each project can be skipped individually by using the environment variable SKIP_PROJECT_NAME_WASM_BUILD. Where PROJECT_NAME needs to be replaced by the name of the cargo project, e.g. node-runtime will be NODE_RUNTIME.


Wasm builder requires the following prerequisites for building the Wasm binary:

  • rust nightly + wasm32-unknown-unknown toolchain

If a specific rust nightly is installed with rustup, it is important that the wasm target is installed as well. For example if installing the rust nightly from 20.02.2020 using rustup install nightly-2020-02-20, the wasm target needs to be installed as well rustup target add wasm32-unknown-unknown --toolchain nightly-2020-02-20.

License: Apache-2.0


~70K SLoC