A low-ish level tool for easily writing and hosting WASM based plugins.

Alec Deason

Last update: Sep 20, 2022

Related tags

Overview

A low-ish level tool for easily writing and hosting WASM based plugins.

The goal of wasm_plugin is to make communicating across the host-plugin boundary as simple and idiomatic as possible while being unopinionated about how you actually use the plugin.

Loading a plugin is as simple as reading the .wasm file off disk.

let mut plugin = WasmPlugin::load("path/to/plugin.wasm")?;

Calling functions exported by the plugin takes one of two forms. Either the function takes no arguments and returns a single serde deserializable value:

let response: ResultType = plugin.call_function("function_name")?;

Or it takes a single serializable argument and returns a single result:

let message = Message::default();
let response: ResultType = plugin.call_function_with_argument("function_name", &message)?;

Exporting a function from a plugin is just a matter of wrapping it in a macro:

fn local_hello() -> String {
    "Hello, host!".to_string()
}
wasm_plugin_guest::export_plugin_function_with_no_input(hello, local_hello);

API Stability

I am not currently guaranteeing any stability, expect all releases to include breaking changes.

Annotation to easily define ad-hoc / one-shot extension traits

2 Apr 19, 2022

Convert Hygea calendar to an iCal file to easily import it to Google Calendar (Rust version)

Hygea to iCal Goal Hygea provides a calendar via PDF and an application called Recycle. I just wanted to use an iCal file to import it in my calendar.

2 Oct 28, 2021

Easily sync your clipboard between devices. This is a work in progress app.

Clipboard Sync Description Easily sync your clipboard between devices. This is a work in progress app. Stack Frontend: React Tauri isomorphic-ws TSX,

2 Mar 2, 2022

PM-Tools - a simple Rust util to easily create server directories

PM-Tools PM-Tools is a simple Rust util to easily create server directories or plugins without the hassle of unzipping or creating directories Progres

2 Mar 19, 2022

Easily customizable command runner made with Rust 🦀

Easily customizable command runner made with Rust 🦀 📦 Usage Install by the following command: cargo install rxe Or build from the source. git clone

4 May 25, 2022

Easily add emojis to your git commit messages 😎

gimoji A CLI tool that makes it easy to add emojis to your git commit messages. It's very similar to (and is based on) gitmoji-cli but written in Rust

12 May 29, 2023

Cargo subcommand to easily bootstrap nocode applications. Write nothing; deploy nowhere.

cargo-nocode No code is the best way to write secure and reliable applications. Write nothing; deploy nowhere. cargo-nocode aims to bring the nocode a

29 Jul 1, 2023

hado-rshado — A little macro for writing haskell-like do expressions without too much ceremony

hado Monadic haskell-like expressions brought to rust via the hado! macro What? A little macro for writing haskell-like do expressions without too muc

44 Jul 31, 2022

A Rust macro for writing regex pattern matching.

regexm A Rust macro for writing regex pattern matching.

46 Oct 24, 2022

Comments

Wasmtime Support

Hello, I came across this project, and I was interested in using it for prototyping my own, however I was planning on using wasmtime as my engine and see that this project only supports wasmer. Would you be up for changing, or accepting a change that adds wasmtime support?

opened by XAMPPRocky 5
Generics for serializer selection

The feature based serializer selection is awkward to use and impossible for users to extend. It should be possible to do it via a type parameter on WasmPlugin and I think that would be a better approach.

opened by alec-deason 0
Support Wasm hosts

When I initially did technology review on Wasmer I saw that they had a javascript package for working with wasm in browser. I made the, as it turns out, very incorrect assumption that that meant the Rust version of the Wasmer engine could itself be compiled to wasm and run in browser and that that would make supporting wasm_plugin in browser easy. I was wrong. Wasmer's JS support is a separate code base which means I will have to provide wasm support some other way, either by calling out to Wasmer's JS tools through my compatibility layer or by using the browser's wasmer api directly, not sure yet.

opened by alec-deason 0