Error thrown when the current page cannot initialize the Wasmer browser runtime.
Configuration used to start a browser-only Wasmer shell process.
Configuration for a Wasmer-backed terminal addon.
Result produced after a WasmerAddon attaches a shell to a terminal.
Result of checking whether the current browser can run Wasmer WASIX processes.
A WebC package already loaded into memory.
Public operations on a shared Wasmer virtual directory.
A directory entry returned by a Wasmer virtual filesystem.
Custom initialization values forwarded to @wasmer/sdk. The first initialization wins.
Structural subset of a running @wasmer/sdk instance used by the transport adapter.
Final output and exit status returned by a Wasmer process.
A Wasmer package resolved by registry name.
Configuration for the Wasmer runtime shared by a shell process.
Features provided by a managed Wasmer shell session.
Managed byte streams and lifecycle for a running Wasmer shell.
A self-hosted WebC package resolved by URL.
A raw WASI or WASIX WebAssembly module loaded directly by Wasmer.
A browser feature required by the Wasmer JavaScript SDK.
Initial files for a WASIX virtual directory, keyed by path.
Mount value accepted when starting a Wasmer shell.
Supported sources for a runnable Wasmer package.
Lifecycle states of a managed Wasmer shell session.
A chunk produced by a Wasmer process output stream.
Throws a diagnostic error unless the current browser can run Wasmer.
Creates a shared virtual directory that can be mounted into one or more Wasmer processes.
Creates a managed terminal session around an already-running Wasmer process. This consumes the
instance through its wait() operation.
Loads a Wasmer package, starts its entrypoint or a named command, and returns a managed session.
Checks browser and isolation features required by @wasmer/sdk.
Initializes the process-wide Wasmer SDK. Repeated calls share one initialization; options from the first call are used.
Adapts a running Wasmer instance to gespenst's native byte transport. Process output
receives the default PTY ONLCR behavior because the Wasmer SDK exposes pipes, not a TTY.
Browser-terminal addon that starts and attaches a Wasmer WASIX shell.