How shm11c3/hardwarevisualizer works
Project type and purpose
• HardwareVisualizer is a cross-platform desktop application built with Tauri.
• It pairs a React/TypeScript frontend (rendered in a WebView) with a Rust backend that gathers hardware metrics, persists them, and exposes them to the UI.
• Use-cases include real-time monitoring, historical insights, customizable dashboards, and background image support.
File structure
• Top-level “src” directory: frontend code (Vite + React + TypeScript + RSPC for RPC).
• “src-tauri” directory: Rust backend code (Cargo.toml, src/main.rs, build.rs, commands, services, database, tests).
• Configuration files: tsconfig.json, vite.config.ts, tauri.conf.json, workflows under .github/workflows.
• Tests split into frontend unit tests (vitest) and Rust integration/tests.
• Utilities and library code in “src/lib” (TypeScript) and “src-tauri/src/utils” (Rust).
README for additional insights
• Confirms Tauri, Node.js, Rust versions.
• Describes features: CPU, RAM, GPU, storage, network metrics; history insights; customizable UI.
• Outlines development commands, platform support, and build steps.
Elements
• Clear labels:
– “React Renderer”
– “RSPC / Tauri Bridge”
– “Rust Command Handlers”
– “Hardware Services”
– “SQLite Database”
– “OS Metrics APIs”
– UI → RPC → Commands → Services → OS
– Services → DB → RPC → UI (for historical data)
– Backend modules in another (e.g., green)
– Frontend, IPC layer, Backend (sub-modules), External Systems.