📄️ Host SDKs
In Extism parlance, we call the application that your plug-ins extend the host. e.g: in VS Code, if the extensions are the plug-ins then the editor itself is the host.
📄️ Host Functions
If you find yourself wanting to provide a plug-in with more custom capabilities, beyond what Extism
📄️ Plug-in Development Kits (PDKs)
Using an official Plug-in Development Kit (PDK) makes it simple to write code which can be compiled to WebAssembly and run within an Extism Host environment.
📄️ The Manifest
The manifest is a description of your plugin and some of the runtime constraints to apply to it. You can think of it as a blueprint to build your plugin.
📄️ Configuration
Configuration for both Host and Plug-in environments is still being worked on, and we expect to collaborate with users on exactly how it should be done. Please reach out on GitHub or join the Discord and share your thoughts.
📄️ Runtime APIs
The Extism runtime is implemented as a Rust crate, from which we generate C headers so that any language with a C-compatible FFI can bind functions to the runtime itself and embed Extism. This is how the official SDKs are created.
📄️ Contributing
Process