ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to define async Rust commands with #[tauri::command], share state via tauri::State, and keep the UI responsive while avoiding a bundled Node.js runtime.
A decision guide for Electron developers on implementing context isolation versus node integration to secure renderer processes and prevent RCE vulnerabilities.
Learn how Tauri's IPC system securely bridges web frontends with Rust backends using commands, with practical examples for building safe, performant desktop applications.
Learn how to bridge the Rust backend and JS frontend in Tauri using the command pattern, managing thread-safe state, and avoiding JSON serialization bottlenecks.
Learn how to expose only the needed IPC methods to your renderer using Electron's Context Isolation and ContextBridge, preventing accidental Node.js leakage.
Keep Electron renderers unprivileged by using contextIsolation, a preload bridge, and validated IPC. This guide shows the smallest suitable architecture, trust boundaries, operational checks, and when to adjust the design.
Practical migration guide for moving legacy Electron apps to context isolation with secure IPC design, version-aware configuration, and incremental renderer refactoring.
Learn how Electron’s context isolation and contextBridge let you expose safe, limited APIs from the preload script to the renderer, keeping Node access locked down.
Goal: Identify which Rust functions are exposed to the webview via Tauri’s invoke IPC in a Tauri 2.x application and understand the default deny behavior that blocks unlisted commands. Constraints: The permission schema in tauri.conf.json has changed from the v1 allowlist to a capabilities file in v2. A missing or malformed entry causes the invoke call to re
rust
tauri
electron