Wasmer Manifest

The manifest file called wasmer.toml is required to publish to the Wasmer registry (opens in a new tab); This file contains the package's dependencies, metadata, and commands are declared.


If you want to get assistance creating the wasmer.toml file you can simply run wasmer init in your directory and the CLI will guide you!

The manifest file contains 4 sections:


Valid keys are:

  • name (string) required
  • version (semver version (opens in a new tab)) required: a valid Semantic Version.
  • description (string) required
  • license (spdx identifier (opens in a new tab)): can be MIT or GPL, for example.
  • license-file (path): an override for the license file path used in publishing. Left undefined, the LICENSE file will be implicitly included in the package.
  • readme (path)
  • repository (url)
  • homepage (url)
  • entrypoint (string): The command to use by default


  • "<namespace>/<name>" = "<version>"


  • name (string) required
  • source (path) required: path to the .wasm file
  • abi (enum): one of: wasi, emscripten, or none


  • name required (string): the name of the command, invoked via wasmer run . --command=<command-name>
  • module required (string): the name of the module this command is running.
  • package required (string): the package name that the module is in.
  • main_args
  • package


  • "location/on/wasm"="location/on/publishing/machine": bundle local files into the package and make them available on the WASI filesystem