Document _app crate convention for Dioxus WASM frontends #48

New issue

Closed

opened 2026-03-05 14:16:34 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-03-05 14:16:34 +00:00

Owner

Problem

The hero_service skill defines three crate suffixes: _server, _sdk, _ui. However, some services (like hero_os) have a Dioxus WASM frontend crate that compiles to static assets. This crate was originally named hero_os_ui, which conflicted with the _ui suffix reserved for the Axum HTTP admin panel.

Solution

Introduce the _app suffix for Dioxus WASM frontend crates:

_app = build-time crate, compiles Rust to WASM assets via dx build
_ui = deployed service, serves those assets + proxies /rpc to _server
_app is not a deployed service — no socket, no binary, no TOML definition

Example: hero_os_app compiles to WASM, hero_os_ui serves those assets.

Affected repos

hero_os — renamed hero_os_ui (Dioxus) → hero_os_app in PR #19

## Problem The hero_service skill defines three crate suffixes: `_server`, `_sdk`, `_ui`. However, some services (like `hero_os`) have a Dioxus WASM frontend crate that compiles to static assets. This crate was originally named `hero_os_ui`, which conflicted with the `_ui` suffix reserved for the Axum HTTP admin panel. ## Solution Introduce the `_app` suffix for Dioxus WASM frontend crates: - `_app` = build-time crate, compiles Rust to WASM assets via `dx build` - `_ui` = deployed service, serves those assets + proxies `/rpc` to `_server` - `_app` is **not** a deployed service — no socket, no binary, no TOML definition Example: `hero_os_app` compiles to WASM, `hero_os_ui` serves those assets. ## Affected repos - `hero_os` — renamed `hero_os_ui` (Dioxus) → `hero_os_app` in PR #19