tawasuyu

tawasuyu/llimphi

Sovereign retained-mode GPU UI framework in Rust (wgpu+vello+taffy+parley), Elm loop, 40+ widgets.

Rust 660Markdown 302TOML 157RON 312382 Definiciones

⎇ main llimphi-wasm-wasi/README.md Markdown · 22 líneas · 1.0 KB Historia crudo

chore: refresco desde el monorepo — 27 crates nuevos (anim, lottie, svg, mesh, image, layer, test, wire-view, widgets rag-sidebar/router/lazy-list/rive-button) y sync de los 95 existentes 93253cc22 · Sergio ·

1# llimphi-wasm-wasi
2
3Runs **console WASI apps** over wasmi.
4
5The catalog is not a trick: besides the Tier 3 apps (UI, our own
6`wasm_view → WireNode` ABI), the bulk of public WASM is **command-line
7programs** compiled to `wasm32-wasi`: they import `wasi_snapshot_preview1`, have a
8`_start` and write to stdout. This crate runs them: a minimal WASI preview1 shim
9instantiates the module, captures its stdout/stderr and returns the output plus
10the exit code. It is not a GUI — it is a console, which is exactly what those
11modules are.
12
13Honest scope: it covers the subset a typical CLI tool uses (write, read stdin,
14args, env, clock, random, exit). Anything touching a **real filesystem or
15sockets** is absent (those imports are not linked: a module using them traps at
16instantiation — the same physical boundary as the rest of the runtime). The
17component model and web apps (wasm-bindgen/DOM) are another story: they need a
18different runtime or a browser (that is `puriy`).
19
20---
21
22Part of **llimphi** — see [llimphi](../README.md).

README.md

llimphi-wasm-wasi

Runs console WASI apps over wasmi.

The catalog is not a trick: besides the Tier 3 apps (UI, our own wasm_view → WireNode ABI), the bulk of public WASM is command-line programs compiled to wasm32-wasi: they import wasi_snapshot_preview1, have a _start and write to stdout. This crate runs them: a minimal WASI preview1 shim instantiates the module, captures its stdout/stderr and returns the output plus the exit code. It is not a GUI — it is a console, which is exactly what those modules are.

Honest scope: it covers the subset a typical CLI tool uses (write, read stdin, args, env, clock, random, exit). Anything touching a real filesystem or sockets is absent (those imports are not linked: a module using them traps at instantiation — the same physical boundary as the rest of the runtime). The component model and web apps (wasm-bindgen/DOM) are another story: they need a different runtime or a browser (that is puriy).


Part of llimphi — see llimphi.