Fission

Tauri Desktop Workflow

The fission-tauri crate hosts the optional desktop UI. This wiki page covers how to run and iterate locally; product behavior stays aligned with the same engines used by the CLI.

Prerequisites

In addition to Rust (see Installation prerequisites):

Node.js and npm for the front-end bundle under crates/fission-tauri/.
Platform-specific requirements from the upstream Tauri toolchain (WebView dependencies on Linux, Xcode tooling on macOS for some setups, MSVC + WebView2 runtime considerations on Windows).

The crate template references IDE plugins for Tauri and rust-analyzer in crates/fission-tauri/README.md.

Install JavaScript dependencies

From the repository root:

cd crates/fission-tauri
npm ci

Use npm ci in CI-like clean installs; use npm install only when intentionally updating lockfiles.

Development mode

Typical iteration loop:

cd crates/fission-tauri
npm run tauri dev

(or cargo tauri dev if that matches your local tauri-cli setup—follow docs/CLI.md / crate conventions).

Hot reload behavior depends on the Tauri + front-end toolchain version pinned by package-lock.json.

Release-style builds

For a production-like artifact:

cd crates/fission-tauri
npm run build

Exact scripts are defined in crates/fission-tauri/package.json. Adjust targets (tauri build) per upstream Tauri docs when cross-compiling.

Logs and debugging

Prefer capturing Rust-side logs from the process stderr and any tracing hooks configured in the desktop shell.
For WebView/front-end issues, use the usual browser devtools attachment workflow described in current Tauri documentation for your major version.

Headless reproducibility for benchmarks and CI continues to favor fission-cli; treat the desktop UI as an interactive lens on the same pipeline where possible.

Repository overview and maturity: README.md
CLI reference (behavioral parity expectations): docs/CLI.md

This site is open source. Improve this page.