myxelium
e49b3ec112
- `LIVE_RELOAD=false npm run dev` keeps the renderer alive across a machine suspend; the reload client otherwise destroys the session under test. - `dev-peer.sh` plus a separate userdata dir runs a second local peer. - `tools/voice-probe.js` samples peer state and RTP counters from a live window, persisting to localStorage so a renderer reload cannot erase it. - e2e helpers for voice pairs, peer-role election, and a TURN relay. - Electron single-instance and dev-client-load decisions move into rules files with colocated specs.
Electron Shell
Electron main-process package for MetoYou / Toju. This directory owns desktop bootstrap, the preload bridge, IPC handlers, desktop persistence glue, updater integration, and window-level behavior.
Commands
npm run build:electronbuilds the Electron TypeScript output todist/electron.npm run electronbuilds the product client and Electron, then launches the desktop app.npm run electron:devstarts the Angular client and Electron together.npm run devstarts the full desktop stack: server, Angular client, and Electron.npm run electron:build,npm run electron:build:win,npm run electron:build:mac, andnpm run electron:build:linuxcreate packaged desktop builds.
Structure
| Path | Description |
|---|---|
main.ts |
Electron app bootstrap and process entry point |
preload.ts |
Typed renderer-facing preload bridge |
process-list.ts |
Linux/Windows process-name scan used as a fallback when foreground detection is unavailable |
game-detection/ |
Foreground-window detection (get-windows + Hyprland/Sway fallbacks) plus pure heuristics scoring and ignore-list filtering |
app/ |
App lifecycle and startup composition |
ipc/ |
Renderer-invoked IPC handlers |
cqrs/ |
Local database command/query handlers and mappings |
db/, entities/, migrations/ |
Desktop persistence and schema evolution |
audio/ |
Desktop audio integrations |
update/ |
Desktop updater flow |
window/ |
Window creation and window-level behavior |
Notes
- When adding a renderer-facing capability, update the Electron implementation,
preload.ts, and the renderer bridge intoju-app/together. - Plugin client data is stored in the local Electron SQLite database in the dedicated user-scoped
plugin_datatable. Renderer plugins reach it through CQRS commands/queries exposed by the preload bridge; the signal server must not be used for arbitrary plugin data persistence. - Treat
dist/electron/anddist-electron/as generated output. - See AGENTS.md for package-level editing rules.