#wit #webassembly #component #input


Tooling for working with *.wit and component files together

16 releases (5 breaking)

0.7.4 Mar 10, 2023
0.7.3 Mar 6, 2023
0.7.1 Feb 23, 2023
0.6.0 Feb 10, 2023
0.0.0 May 10, 2022

#41 in #webassembly

Download history 304/week @ 2022-12-05 326/week @ 2022-12-12 291/week @ 2022-12-19 159/week @ 2022-12-26 284/week @ 2023-01-02 230/week @ 2023-01-09 583/week @ 2023-01-16 596/week @ 2023-01-23 868/week @ 2023-01-30 801/week @ 2023-02-06 1442/week @ 2023-02-13 1110/week @ 2023-02-20 952/week @ 2023-02-27 1300/week @ 2023-03-06 1053/week @ 2023-03-13 1289/week @ 2023-03-20

4,663 downloads per month
Used in 17 crates (14 directly)

Apache-2.0 WITH LLVM-exception

32K SLoC


wit-component is a crate for creating and interacting with WebAssembly components based on the component model proposal.

CLI usage

The wit-component crate is available through the wasm-tools CLI suite under two subcommands:

# Create a component from the input core wasm module
$ wasm-tools component new core.wasm -o component.wasm

# Extract a `*.wit` interface from a component
$ wasm-tools component wit component.wasm


  • Creates WebAssembly component binaries from input core WebAssembly modules. Input modules communicate with the canonical ABI to imported and exported interfaces described with *.wit files. The wit interface is either embedded directly in the core wasm binary.

  • Supports "adapters" which can be used to bridge legacy core WebAssembly imported functions into component model functions. Adapters are themselves core wasm binaries which will be embedded into the final component. An adapter's exports can be imported by the main core wasm binary and the adapter can then call component model imports.

  • A *.wit interface can be extracted from an existing component to see the interface that it exports and intends to import.


Note that this crate is intended to be a low-level detail of tooling for components. Developers will not necessarily interact with this tooling day-to-day, instead using wrappers such as cargo-component which will automatically execute wit-component to produce component binaries.

First wit-component supports the wasm-based encoding of a WIT package:

$ cat demo.wit
interface host {
  hello: func()
default world demo {
  import host: self.host

$ wasm-tools component wit demo.wit -o demo.wasm --wasm

# The output `demo.wasm` is a valid component binary
$ wasm-tools validate --features component-model demo.wasm
$ wasm-tools print demo.wasm

# The `*.wit` file can be recovered from the `demo.wasm` as well
$ wasm-tools component wit demo.wasm

Toolchain authors can use wit-component to embed this component types section into a core wasm binary. For a small demo here a raw *.wat wasm text file will be used where the demo.wit argument is specified manually, however.

$ cat demo.core.wat
  (import "host" "hello" (func))

$ wasm-tools component embed demo.wit --world demo demo.core.wat -o demo.wasm

# See that there's a new `component-type` custom section
$ wasm-tools objdump demo.wasm

# Convert the core wasm into a component now
$ wasm-tools component new demo.wasm -o demo.component.wasm

# Like before the output `demo.wasm` is a valid component binary
$ wasm-tools validate --features component-model demo.component.wasm
$ wasm-tools print demo.component.wasm

# Additionally like before the `*.wit` interface can still be extracted
$ wasm-tools component wit demo.component.wasm

Here the demo.component.wasm can now be shipped to a component runtime or embedded into hosts.


~125K SLoC