Rust shell · platform webview · Bun toolchain
A desktop app that ships as a binary, not a folder.
Voussoir is a thin load-bearing shell around the webview your operating system already has. The frontend compiles into the executable, so the artifact contains no Chromium, no Node and no runtime to install.
voussoir init notes
# 12 files, 3 of them config
Init should hand you an app, not an archaeology project
Most frameworks answer init with a bundler config, a plugin manifest,
capability files and a folder per feature. You will not open most of them, and none of
them are yours. The cost is not disk space. It is that nobody can hold the structure in
their head, so every change starts with working out what wrote a file and what breaks if
you delete it.
files in a new app
Three are configuration or housekeeping. The other nine are the app.
direct dependencies
wry, tao, serde_json and serde. Everything else is a feature you opt into.
minimal release binary
No V8, no Chromium, no node_modules. The webview belongs to the OS.
Install
One script installs the system webview, Git, Bun and Rust, builds the CLI, and puts
voussoir on PATH. Re-running it is an upgrade: every dependency
that is already there is skipped.
Linux, macOS and the BSDs
curl -fsSL https://raw.githubusercontent.com/smegasberla/voussoir/master/install.sh | sh
Windows
irm https://raw.githubusercontent.com/smegasberla/voussoir/master/install.ps1 | iex
Then, once, in any directory:
voussoir init notes && cd notes && voussoir dev
Flags: --prefix, --no-deps, --repo
(-Prefix, -NoDeps, -Repo on Windows).
Voussoir is not published to crates.io or npm yet, so the scripts and a checkout are the
only ways in.
One endpoint, one envelope
The page and Rust share a single JSON contract. A reply is the reply, with an error kind the page can branch on instead of matching message text.
POST voussoir://localhost/__voussoir/<method>
body: <payload as JSON, or null>
response: {"ok": <json>}
| {"error": {"message": "<text>", "kind": "<class>", "method": "<name>"}}
const greeting = await window.voussoir.invoke<string>("greet", { name: "you" });
Registered handlers are the allowlist, decided at compile time, so there are no capability files to keep in sync with the code.
Read the docs
33 chapters, from an empty directory to a signed installer.