ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A decision guide for Tauri developers choosing between commands, events, or a custom protocol to expose Rust backend functionality, covering security, payload size, and streaming trade‑offs with concrete code examples.
Tauri commands are the supported bridge between Rust and your web UI. Treat them as a serialized request/response boundary: design payloads carefully, guard shared state, and avoid high-frequency invoke loops.
A practical look at using contextIsolation, preload scripts, and contextBridge to keep Electron renderer processes from accessing Node.js directly.
Expose a limited API from Electron's preload script to the renderer with contextBridge, keeping Node integration disabled.
Learn how to restrict which native commands each Tauri window can call by using capability scopes, reducing attack surface while keeping the app functional.
Electron's contextBridge lets you expose a narrow, audited API from the main process to the renderer. Here is how to replace nodeIntegration with an explicit IPC contract, with a worked file-read example.
In Tauri 2.x, treat Rust commands as a validated API boundary rather than a generic file bridge. A worked note-saver example shows path canonicalization, error mapping, and capability caveats.
Learn how to use the Tauri Isolation Pattern to prevent XSS attacks from becoming Remote Code Execution (RCE) vulnerabilities by intercepting IPC messages.
Electron's context isolation wall is deliberate — and contextBridge is the only door through it. A practical walkthrough of the preload/main/renderer pattern, Structured Clone pitfalls, and the escape hatches to avoid.
rust
tauri
electron