embedding-tauri-sidecars

You can embed external binaries in Tauri apps by configuring them in tauri.conf.json under bundle.externalBin, then spawning and managing them at runtime using tauri_plugin_shell APIs in Rust or JavaScript.

A Tauri sidecar is an external binary embedded inside your app to extend functionality without shipping heavy dependencies. You need it when your app must run platform-specific tools or data processors without requiring users to install them separately.

Configure cross-platform binaries in tauri.conf.json under bundle.externalBin by naming your binaries with platform-specific target triples, ensuring Tauri bundles the correct variant for each operating system at runtime.

Yes, you can spawn sidecars from JavaScript using tauri_plugin_shell APIs, which support passing arguments, streaming output, and managing the binary lifecycle directly from your frontend code.

Yes, Tauri provides both Rust and JavaScript APIs via tauri_plugin_shell to spawn, monitor, and communicate with sidecar processes, handling arguments, streaming output, and safe lifecycle management at runtime.

Limitations of embedding external binaries include the need for careful configuration in tauri.conf.json, strict platform-specific binary naming with target triples, and the requirement to manually manage safe process lifecycles via tauri_plugin_shell.