WASM Sandbox Runtime

Experimental status

WASM sandbox runtime is experimental for @omnicajs/vue-remote. The library can be used in this environment via custom adapters, but full support is currently not guaranteed.

Why consider it

strict compute/runtime isolation goals;
portability across host environments;
controlled execution model for extension logic.

Integration model

@omnicajs/vue-remote still expects channel semantics. WASM guest and host bridge must exchange messages in a compatible endpoint protocol.

// Pseudocode

const sandbox = createWasmSandbox()
const bridge = createWasmMessageBridge(sandbox) // MessageEndpoint-like adapter

const endpoint = createEndpoint<RemoteApi>(bridge)
await endpoint.call.run(receiver.receive, hostBridge)

Practical constraints

Bridge complexity is high (guest-host marshalling, ownership, lifecycle).
Debugging and observability require dedicated tooling.
Performance profile depends heavily on bridge design.
Production rollout usually needs staged validation and fallback paths.

Guidance

Use this mode for advanced experimentation and platform R&D.
Keep protocol compatibility tests around run/release and update flow.
Do not assume baseline transport parity without explicit validation.