CodeVetter · Repo Unpack · Extension points
tauri-apps/tauri
Tauri is designed for extension at several layers: Rust commands registered through `generate_handler!`/`#[command]`, full plugins implementing the `Plugin` trait (with the companion `tauri-plugin` build crate emitting permissions, global API scripts and mobile glue), custom URI scheme protocols, Builder lifecycle hooks (setup, page-load, menu/tray/window/webview events, channel interceptor), custom `Assets` providers, a swappable `Runtime` trait, capability/permission JSON+TOML files composing ACLs, `State` injection for shared data, and JS-side extension via `Channel`, `Resource` and the `__TAURI_TO_IPC_KEY__` serialization hook.
- The `Plugin<R>` trait is the primary extension interface: implementors provide `name()` plus optional `initialize`, `initialization_script`/`initialization_script_2`, `window_created`, `webview_created`, `on_navigation` (veto navigation), `on_page_load`, `on_event` and a cleanup hook.
- Plugins are attached via `Builder::plugin`/`AppHandle::plugin`/`plugin_boxed` and stored in `PluginStore`; commands addressed as `plugin:<name>|<command>` are routed to the plugin's invoke handler by `run_plugin_invoke_handler`.
- App commands are registered with `#[tauri::command]` fns collected by `tauri::generate_handler![...]` into the `InvokeHandler` passed to `Builder::invoke_handler` — the command table macro lives in tauri-macros/src/command (wrapper.rs + handler.rs).
- Plugin build-time integration: `tauri_plugin::build::Builder::new(commands)` accepts `global_scope_schema`, `global_api_script_path`, `android_path`, `ios_path` and emits artifacts (permissions, api scripts, mobile code) consumed by tauri-build/context_codegen via OUT_DIR files.
- Custom URI scheme protocols plug in through `UriSchemeProtocol` handlers registered on the WebviewManager (`register_uri_scheme_protocol`), with `UriSchemeContext`/`UriSchemeResponder` exposed for async responses.
- Builder hooks are extension points: `setup`, `on_page_load`, `on_menu_event`, `on_tray_icon_event`, `on_window_event`, `on_webview_event`, `invoke_system` and `channel_interceptor` all accept user closures stored on the Builder struct.
- The `Assets<R>` trait abstracts asset retrieval (`get`, `iter`, `csp_hashes`); ContextData accepts a custom `assets` Expr so embedders can replace EmbeddedAssets entirely.
- The `Runtime`/`RuntimeHandle` traits (wrapping tauri-runtime) let apps swap the webview backend; `Builder` is generic over `R: Runtime` and `wry` is just the default via `default_runtime` macro.
- ACL extension: apps declare capabilities JSON (and plugin permission TOML via `define_permissions`) that `get_capabilities` + `Resolved::resolve` merge at codegen time; `dynamic-acl` additionally permits runtime `add_capability`.
- Shared state plugs into commands through `app.manage(...)` (StateManager) and the `State<'_, T>` command arg extractor; resources use `ResourceTable` with rid handles exposed to JS as the `Resource` class.
- The CLI itself is extensible by adding a `Commands` variant + module in crates/tauri-cli/src, and `tauri plugin init/new` scaffolds new plugins from crates/tauri-cli/templates.
- JS-side custom serialization: any object implementing `[SERIALIZE_TO_IPC_FN]` (`__TAURI_TO_IPC_KEY__`) controls its IPC representation — the mechanism `Channel` uses to serialize itself as `__CHANNEL__:<id>`.