listening-to-tauri-events
Teaches how to subscribe to and listen for Tauri events in the frontend using the events API, including typed event handlers and cleanup patterns.
What this skill does
# Listening to Tauri Events in the Frontend
This skill covers how to subscribe to events emitted from Rust in a Tauri v2 application using the `@tauri-apps/api/event` module.
## Core Concepts
Tauri provides two event scopes:
1. **Global events** - Broadcast to all listeners across all webviews
2. **Webview-specific events** - Targeted to specific webview windows
**Important:** Webview-specific events are NOT received by global listeners. Use the appropriate listener type based on how events are emitted from Rust.
## Installation
The event API is part of the core Tauri API package:
```bash
npm install @tauri-apps/api
# or
pnpm add @tauri-apps/api
# or
yarn add @tauri-apps/api
```
## Global Event Listening
### Basic Listen Pattern
```typescript
import { listen } from '@tauri-apps/api/event';
// Listen for a global event
const unlisten = await listen('download-started', (event) => {
console.log('Event received:', event.payload);
});
// Clean up when done
unlisten();
```
### Typed Event Payloads
Define TypeScript interfaces matching your Rust payload structures:
```typescript
import { listen } from '@tauri-apps/api/event';
// Define the payload type (matches Rust struct with camelCase)
interface DownloadStarted {
url: string;
downloadId: number;
contentLength: number;
}
// Use generic type parameter for type safety
const unlisten = await listen<DownloadStarted>('download-started', (event) => {
console.log(`Downloading from ${event.payload.url}`);
console.log(`Content length: ${event.payload.contentLength} bytes`);
console.log(`Download ID: ${event.payload.downloadId}`);
});
```
### Event Object Structure
The event callback receives an `Event<T>` object:
```typescript
interface Event<T> {
/** Event name */
event: string;
/** Event identifier */
id: number;
/** Event payload (your custom type) */
payload: T;
}
```
## Webview-Specific Event Listening
For events emitted with `emit_to` or `emit_filter` targeting specific webviews:
```typescript
import { getCurrentWebviewWindow } from '@tauri-apps/api/webviewWindow';
const appWebview = getCurrentWebviewWindow();
// Listen for events targeted to this specific webview
const unlisten = await appWebview.listen<string>('login-result', (event) => {
if (event.payload === 'loggedIn') {
localStorage.setItem('authenticated', 'true');
} else {
console.error('Login failed:', event.payload);
}
});
```
## One-Time Event Listeners
Use `once` for events that should only be handled a single time:
```typescript
import { once } from '@tauri-apps/api/event';
import { getCurrentWebviewWindow } from '@tauri-apps/api/webviewWindow';
// Global one-time listener
await once('app-ready', (event) => {
console.log('Application is ready');
});
// Webview-specific one-time listener
const appWebview = getCurrentWebviewWindow();
await appWebview.once('initialized', (event) => {
console.log('Webview initialized');
});
```
## Cleanup and Unsubscription
### Manual Cleanup
Always unsubscribe listeners when they are no longer needed:
```typescript
import { listen } from '@tauri-apps/api/event';
const unlisten = await listen('my-event', (event) => {
// Handle event
});
// Later, when done listening
unlisten();
```
### React Component Cleanup
```typescript
import { useEffect } from 'react';
import { listen } from '@tauri-apps/api/event';
interface ProgressPayload {
percent: number;
message: string;
}
function DownloadProgress() {
useEffect(() => {
let unlisten: (() => void) | undefined;
const setupListener = async () => {
unlisten = await listen<ProgressPayload>('download-progress', (event) => {
console.log(`Progress: ${event.payload.percent}%`);
});
};
setupListener();
// Cleanup when component unmounts
return () => {
if (unlisten) {
unlisten();
}
};
}, []);
return <div>Listening for progress...</div>;
}
```
### Vue Composition API Cleanup
```typescript
import { onMounted, onUnmounted } from 'vue';
import { listen } from '@tauri-apps/api/event';
interface NotificationPayload {
title: string;
body: string;
}
export default {
setup() {
let unlisten: (() => void) | undefined;
onMounted(async () => {
unlisten = await listen<NotificationPayload>('notification', (event) => {
console.log(`${event.payload.title}: ${event.payload.body}`);
});
});
onUnmounted(() => {
if (unlisten) {
unlisten();
}
});
}
};
```
### Svelte Cleanup
```svelte
<script lang="ts">
import { onMount, onDestroy } from 'svelte';
import { listen } from '@tauri-apps/api/event';
interface StatusPayload {
status: 'idle' | 'loading' | 'complete';
}
let unlisten: (() => void) | undefined;
onMount(async () => {
unlisten = await listen<StatusPayload>('status-change', (event) => {
console.log('Status:', event.payload.status);
});
});
onDestroy(() => {
if (unlisten) {
unlisten();
}
});
</script>
```
## Automatic Listener Cleanup
Tauri automatically clears listeners in these scenarios:
- **Page reload** - All listeners are cleared
- **URL navigation** - Listeners are cleared (except in SPA routers)
**Warning:** Single Page Application routers that do not trigger full page reloads will NOT automatically clean up listeners. You must manually unsubscribe.
## Multiple Event Listeners
### Listening to Multiple Events
```typescript
import { listen } from '@tauri-apps/api/event';
interface DownloadEvent {
url: string;
}
interface ProgressEvent {
percent: number;
}
interface CompleteEvent {
path: string;
size: number;
}
async function setupDownloadListeners() {
const unlisteners: Array<() => void> = [];
unlisteners.push(
await listen<DownloadEvent>('download-started', (event) => {
console.log(`Started downloading: ${event.payload.url}`);
})
);
unlisteners.push(
await listen<ProgressEvent>('download-progress', (event) => {
console.log(`Progress: ${event.payload.percent}%`);
})
);
unlisteners.push(
await listen<CompleteEvent>('download-complete', (event) => {
console.log(`Complete: ${event.payload.path} (${event.payload.size} bytes)`);
})
);
// Return cleanup function
return () => {
unlisteners.forEach((unlisten) => unlisten());
};
}
// Usage
const cleanup = await setupDownloadListeners();
// Later...
cleanup();
```
## Type Definitions Reference
### Creating Typed Event Helpers
```typescript
import { listen, once, Event } from '@tauri-apps/api/event';
// Define all your event types in one place
export interface AppEvents {
'download-started': { url: string; downloadId: number };
'download-progress': { downloadId: number; percent: number };
'download-complete': { downloadId: number; path: string };
'download-error': { downloadId: number; error: string };
'notification': { title: string; body: string };
}
// Type-safe listen helper
export async function listenTyped<K extends keyof AppEvents>(
eventName: K,
handler: (event: Event<AppEvents[K]>) => void
): Promise<() => void> {
return listen<AppEvents[K]>(eventName, handler);
}
// Usage
const unlisten = await listenTyped('download-started', (event) => {
// event.payload is typed as { url: string; downloadId: number }
console.log(event.payload.url);
});
```
## Corresponding Rust Emit Code
For reference, here is how events are emitted from Rust:
### Global Emit
```rust
use tauri::{AppHandle, Emitter};
use serde::Serialize;
#[derive(Clone, Serialize)]
#[serde(rename_all = "camelCase")]
struct DownloadStarted {
url: String,
download_id: usize,
content_length: usize,
}
#[tauri::command]
fn start_download(app: AppHandle, url: String) {
app.emit("download-started", DownloadStarted {
url,
download_id: 1,
content_length: 1024,
}).unwrap();
}
```
### Webview-Specific Emit
```rust
use tauri::{AppHandle, EmitterRelated 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.