calling-rust-from-tauri-frontend
Guides the user through calling Rust backend functions from the Tauri frontend using the invoke function, defining commands with the
What this skill does
# Calling Rust from Tauri Frontend
This skill covers how to call Rust backend functions from your Tauri v2 frontend using the command system and invoke function.
## Overview
Tauri provides two IPC mechanisms:
- **Commands** (recommended): Type-safe function calls with serialized arguments/return values
- **Events**: Dynamic, one-way communication (not covered here)
## Basic Commands
### Defining a Command in Rust
Use the `#[tauri::command]` attribute macro:
```rust
// src-tauri/src/lib.rs
#[tauri::command]
fn greet(name: String) -> String {
format!("Hello, {}!", name)
}
```
### Registering Commands
Commands must be registered with the invoke handler:
```rust
#[cfg_attr(mobile, tauri::mobile_entry_point)]
pub fn run() {
tauri::Builder::default()
.invoke_handler(tauri::generate_handler![greet, login, fetch_data])
.run(tauri::generate_context!())
.expect("error while running tauri application")
}
```
### Invoking from JavaScript/TypeScript
```typescript
import { invoke } from '@tauri-apps/api/core';
const greeting = await invoke('greet', { name: 'World' });
console.log(greeting); // "Hello, World!"
```
Or with the global Tauri object (when `app.withGlobalTauri` is enabled):
```javascript
const { invoke } = window.__TAURI__.core;
const greeting = await invoke('greet', { name: 'World' });
```
## Passing Arguments
### Argument Naming Convention
By default, Rust snake_case arguments map to JavaScript camelCase:
```rust
#[tauri::command]
fn create_user(user_name: String, user_age: u32) -> String {
format!("{} is {} years old", user_name, user_age)
}
```
```typescript
await invoke('create_user', { userName: 'Alice', userAge: 30 });
```
Use `rename_all` to change the naming convention:
```rust
#[tauri::command(rename_all = "snake_case")]
fn create_user(user_name: String, user_age: u32) -> String {
format!("{} is {} years old", user_name, user_age)
}
```
### Complex Arguments
Arguments must implement `serde::Deserialize`:
```rust
use serde::Deserialize;
#[derive(Deserialize)]
struct UserData {
name: String,
email: String,
age: u32,
}
#[tauri::command]
fn register_user(user: UserData) -> String {
format!("Registered {} ({}) age {}", user.name, user.email, user.age)
}
```
```typescript
await invoke('register_user', {
user: { name: 'Alice', email: '[email protected]', age: 30 }
});
```
## Returning Values
### Simple Return Types
Return types must implement `serde::Serialize`:
```rust
#[tauri::command]
fn get_count() -> i32 { 42 }
#[tauri::command]
fn get_message() -> String { "Hello from Rust!".into() }
```
```typescript
const count: number = await invoke('get_count');
const message: string = await invoke('get_message');
```
### Returning Complex Types
```rust
use serde::Serialize;
#[derive(Serialize)]
struct AppConfig {
theme: String,
language: String,
notifications_enabled: bool,
}
#[tauri::command]
fn get_config() -> AppConfig {
AppConfig {
theme: "dark".into(),
language: "en".into(),
notifications_enabled: true,
}
}
```
```typescript
interface AppConfig {
theme: string;
language: string;
notificationsEnabled: boolean;
}
const config: AppConfig = await invoke('get_config');
```
### Returning Binary Data
For large binary data, use `tauri::ipc::Response` to bypass JSON serialization:
```rust
use tauri::ipc::Response;
#[tauri::command]
fn read_file(path: String) -> Response {
let data = std::fs::read(&path).unwrap();
Response::new(data)
}
```
```typescript
const data: ArrayBuffer = await invoke('read_file', { path: '/path/to/file' });
```
## Error Handling
### Using Result Types
Return `Result<T, E>` where `E` implements `Serialize` or is a `String`:
```rust
#[tauri::command]
fn divide(a: f64, b: f64) -> Result<f64, String> {
if b == 0.0 {
Err("Cannot divide by zero".into())
} else {
Ok(a / b)
}
}
```
```typescript
try {
const result = await invoke('divide', { a: 10, b: 0 });
} catch (error) {
console.error('Error:', error); // "Cannot divide by zero"
}
```
### Custom Error Types with thiserror
```rust
use serde::Serialize;
use thiserror::Error;
#[derive(Debug, Error)]
enum AppError {
#[error("File not found: {0}")]
FileNotFound(String),
#[error("Permission denied")]
PermissionDenied,
#[error("IO error: {0}")]
Io(#[from] std::io::Error),
}
impl Serialize for AppError {
fn serialize<S>(&self, serializer: S) -> Result<S::Ok, S::Error>
where S: serde::ser::Serializer {
serializer.serialize_str(self.to_string().as_ref())
}
}
#[tauri::command]
fn open_file(path: String) -> Result<String, AppError> {
if !std::path::Path::new(&path).exists() {
return Err(AppError::FileNotFound(path));
}
let content = std::fs::read_to_string(&path)?;
Ok(content)
}
```
### Structured Error Responses
```rust
use serde::Serialize;
#[derive(Debug, Serialize)]
struct ErrorResponse { code: String, message: String }
#[tauri::command]
fn validate_input(input: String) -> Result<String, ErrorResponse> {
if input.is_empty() {
return Err(ErrorResponse {
code: "EMPTY_INPUT".into(),
message: "Input cannot be empty".into(),
});
}
Ok(input.to_uppercase())
}
```
```typescript
interface ErrorResponse { code: string; message: string; }
try {
const result = await invoke('validate_input', { input: '' });
} catch (error) {
const err = error as ErrorResponse;
console.error(`Error ${err.code}: ${err.message}`);
}
```
## Async Commands
### Defining Async Commands
Use the `async` keyword:
```rust
#[tauri::command]
async fn fetch_data(url: String) -> Result<String, String> {
let response = reqwest::get(&url).await.map_err(|e| e.to_string())?;
let body = response.text().await.map_err(|e| e.to_string())?;
Ok(body)
}
```
### Async with Borrowed Types Limitation
Async commands cannot use borrowed types like `&str` directly:
```rust
// Will NOT compile:
// async fn bad_command(value: &str) -> String { ... }
// Use owned types instead:
#[tauri::command]
async fn good_command(value: String) -> String {
some_async_operation(&value).await;
value
}
// Or wrap in Result as workaround:
#[tauri::command]
async fn with_borrowed(value: &str) -> Result<String, ()> {
some_async_operation(value).await;
Ok(value.to_string())
}
```
### Frontend Invocation
Async commands work identically to sync since `invoke` returns a Promise:
```typescript
const result = await invoke('fetch_data', { url: 'https://api.example.com/data' });
```
## Accessing Tauri Internals
### WebviewWindow, AppHandle, and State
```rust
use std::sync::Mutex;
struct AppState { counter: Mutex<i32> }
#[tauri::command]
async fn get_window_label(window: tauri::WebviewWindow) -> String {
window.label().to_string()
}
#[tauri::command]
async fn get_app_version(app: tauri::AppHandle) -> String {
app.package_info().version.to_string()
}
#[tauri::command]
fn increment_counter(state: tauri::State<AppState>) -> i32 {
let mut counter = state.counter.lock().unwrap();
*counter += 1;
*counter
}
pub fn run() {
tauri::Builder::default()
.manage(AppState { counter: Mutex::new(0) })
.invoke_handler(tauri::generate_handler![
get_window_label, get_app_version, increment_counter
])
.run(tauri::generate_context!())
.expect("error while running tauri application")
}
```
## Advanced Features
### Raw Request Access
Access headers and raw body:
```rust
use tauri::ipc::{Request, InvokeBody};
#[tauri::command]
fn upload(request: Request) -> Result<String, String> {
let InvokeBody::Raw(data) = request.body() else {
return Err("Expected raw body".into());
};
let auth = request.headers()
.get("Authorization")
.and_then(|v| v.to_str().ok())
.ok_or("Missing Authorization header")?;
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.