This guide covers how to develop WASM/WASIX plugins for Signal K Server. WASM plugins get isolated storage and capability-based permissions. The server's bindings enforce those capabilities; the plugins themselves run in Node.js's built-in WebAssembly runtime (node:wasi), which is not a security boundary for untrusted code.
What Makes a WASM Plugin?
A WASM plugin is an npm package that contains the WASM code for the plugin instead of the traditional JavaScript code. A WASM plugin is identified by the wasmManifest field in package.json:
wasmManifest (required): Path to the compiled .wasm file. This field tells Signal K to load this as a WASM plugin instead of a Node.js plugin.
wasmCapabilities (optional): Declares what permissions the plugin needs (network, storage, etc.). See Plugin Capabilities for the full list.
Package name (flexible): Can be anything - my-plugin, @myorg/my-plugin, etc. There is no requirement to use @signalk/ scope.
Keywords: Include both signalk-node-server-plugin and signalk-wasm-plugin. The App Store finds every plugin by signalk-node-server-plugin; signalk-wasm-plugin marks it as a WASM plugin.
Language Options
Signal K Server supports multiple languages for WASM plugin development: