Configure a Polywrap Manifest

Each Wasm wrapper is orchestrated by a Polywrap Manifest polywrap.yaml file. The Polywrap Manfiest provides the Polywrap CLI with basic information it needs to build the wrapper and generate code bindings with codegen.

Content

The Polywrap Manifest contains the name of the wrapper, programming language used to write it, and the location of the wrapper schema that declares the wrapper's interface.

It optionally includes a path to the wrapper's entry file (e.g. src/index.ts, src/lib.rs) and paths to other manifests that can be used to configure the build and deploy process. It can also contain an array of URI Redirects.

Schema

format: # The manifest format version

name: # Name of wrapper

language: # Wrapper programming language

schema: # Path to wrapper schema

module: # (Optional) Path to entry file

build: # (Optional) Path to Build Manifest file

meta: # (Optional) Path to Meta Manifest file

deploy: # (Optional) Path to wrapper Deploy Manifest file

import_redirects: # (Optional) Array of URI redirects

- uri: # Source URI to be redirected

schema: # Path to schema of the module to which URI will be redirected

Example

format: 0.2.0

project:

name: simple-storage

type: wasm/assemblyscript

source:

schema: ./src/schema.graphql

module: ./src/index.ts

extensions:

build: ./polywrap.build.yaml

meta: ./polywrap.meta.yaml

deploy: ./polywrap.deploy.yaml

import_redirects:

- uri: wrap://ens/imported-wrapper.eth

schema: ./../local-wrapper/schema.graphql