Development

Build and checks

Verified formatting, compilation, type-check, and production-build commands.

These commands come from the repository documentation and the configured package scripts. Run them from the repository root unless noted otherwise.

Desktop application

npm run check:frontend
cargo fmt --check --manifest-path src-tauri/Cargo.toml
cargo check --manifest-path src-tauri/Cargo.toml
npx tauri build --no-bundle

The Rust checks require the Tauri system libraries. QEMU is not required to compile or launch the current shell, but it is required for machine creation and lifecycle operations. The final command builds a release binary without producing an installer bundle.

Website

pnpm typecheck
pnpm build

pnpm typecheck runs TypeScript without emitting files. pnpm build creates a production Next.js build. The website has no configured lint script.

No automated test suite is configured

The repositories do not include automated tests in the inspected state. Do not claim a scenario or VM lifecycle was verified by a test command. Application and virtualization behavior is tested by the maintainer.

Formatting

Rust formatting is checked with cargo fmt --check. The website has no configured formatter script; TypeScript and CSS are maintained manually.

What a passing check means

A passing build means the code compiles and the static checks succeed. It does not prove that a guest operating system boots, that a particular QEMU build exposes the required console transport, or that every guest input and reconnect path works. Those behaviors require the maintainer's scenario testing.

See Contributing for the engineering expectations around these checks.