> For the complete documentation index, see [llms.txt](https://jubianchi.gitbook.io/wasmer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jubianchi.gitbook.io/wasmer-docs/doc-update-1.0/ecosystem/wapm/manifest.md).

# Manifest

The manifest (`wapm.toml`) is optional for using the `wapm` CLI tool; it manages package dependencies, metadata and commands.

However, a manifest is required [to publish](/wasmer-docs/doc-update-1.0/ecosystem/wapm/publishing-your-package.md) to the [WAPM registry](https://wapm.io).

{% hint style="success" %}
If you want to get assistance creating the `wapm.toml` file you can simply run `wapm init` in your directory and the CLI will guide you!
{% endhint %}

The manifest file contains 4 sections:

## \[package]

Valid keys are:

* `name` (string) **required**
* `version` ([semver version](https://semver.org/)) **required**: a valid Semantic Versioning version.
* `description` (string) **required**
* `license` ([spdx identifier](https://spdx.org/licenses/)): 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)
* `wasmer-extra-flags` (string): extra arguments to pass via `wapm run`, for example: `"--backend=singlepass"`)

## \[dependencies]

* `<namespace>/<name>" = "<version>`

## \[\[module]]

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

## \[\[command]]

* `name` **required** (string): the name of the command, invoked via `wapm run <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`

## \[fs]

* `"location/on/wasm"="location/on/host"`: a mapping between paths


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://jubianchi.gitbook.io/wasmer-docs/doc-update-1.0/ecosystem/wapm/manifest.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.