URL instances are fetched and their responses interpreted according to their content-type response header. application/wasm and application/octet-stream items
are treated as ManifestWasmData items; application/json and text/json are treated as JSON-encoded Manifests.
string instances that start with http://, https://, or file:// are treated as URLs.
string instances that start with { treated as JSON-encoded Manifests.
letmanifest = { wasm: [{name:'my-wasm', url:'http://example.com/path/to/wasm'}], config: { 'greeting':'hello'// these variables will be available via `extism_get_var` in plugins } }
Any type that can be converted into an Extism Manifest.
objectinstances that implement Manifest are validated.ArrayBufferinstances are converted into Manifests with a single ManifestWasmData member.URLinstances are fetched and their responses interpreted according to theircontent-typeresponse header.application/wasmandapplication/octet-streamitems are treated as ManifestWasmData items;application/jsonandtext/jsonare treated as JSON-encoded Manifests.stringinstances that start withhttp://,https://, orfile://are treated as URLs.stringinstances that start with{treated as JSON-encoded Manifests.stringinstances are treated as ManifestWasmPath.