fix(dev): honor mesh=1 in desktop-standalone

desktop-standalone was the only launch recipe that ignored the `mesh`
variable. dev, staging and production all build FEATURES=(--features
mesh-llm) when it is set; desktop-standalone invoked `tauri dev` with no
features, so `just mesh=1 desktop-standalone` silently produced a
non-mesh build and the app reported "mesh-llm feature not enabled" from
desktop/src-tauri/src/mesh_llm_stubs.rs.

Wire it up the same way as the other three recipes.

Co-authored-by: Michael Neale <michael.neale@gmail.com>
Signed-off-by: Michael Neale <michael.neale@gmail.com>
This commit is contained in:
Michael Neale
2026-08-20 14:18:24 +10:00
parent 0cd224c2e2
commit 92ecac29ea

View File

@@ -548,7 +548,11 @@ desktop-standalone *ARGS: _ensure-sidecar-stubs
fi
trap '../scripts/cleanup-instance-agents.sh "$INSTANCE_ID" || true' EXIT
echo "Starting standalone desktop on Vite port ${BUZZ_VITE_PORT}; no relay services were started"
pnpm exec tauri dev --config "$BUZZ_TAURI_CONFIG" {{ARGS}}
FEATURES=()
if [[ -n "{{mesh}}" ]]; then
FEATURES=(--features mesh-llm)
fi
pnpm exec tauri dev ${FEATURES[@]+"${FEATURES[@]}"} --config "$BUZZ_TAURI_CONFIG" {{ARGS}}
# Run the desktop app against the internal staging relay (installs deps + builds agent tools automatically)
staging *ARGS: bootstrap _ensure-sidecar-stubs