Tauri
Specific best practices and architectural patterns when working with Tauri.
Details
Language / Topic
TypeScriptCategory
framework
Rules
balanced
Tauri
- Use the Rust backend for system operations — invoke commands via `@tauri-apps/api/core` from the frontend. Define Tauri commands in `src-tauri/src/` with the `#[tauri::command]` macro. Use the permission system in `capabilities/` for security.
Tauri
- Use the Rust backend for system operations — invoke commands via `@tauri-apps/api/core` from the frontend. Define Tauri commands in `src-tauri/src/` with the `#[tauri::command]` macro. Use the permission system in `capabilities/` for security.
- Use `tauri::State<>` for managed application state shared across commands. Handle errors by returning `Result<T, String>` from commands. Use event system (`emit`/`listen`) for backend-to-frontend communication. Configure `tauri.conf.json` for window settings, bundling, and allowed APIs. Use the Tauri plugin ecosystem (`fs`, `dialog`, `shell`) instead of raw system calls.