Skip to main content
The plugin has three installable pieces. The Rust crate is required; the bindings are required if the webview needs to authenticate; the React hooks are optional.

Requirements

The Rust crate

The crate is not on crates.io yet, so consume it as a git dependency.
src-tauri/Cargo.toml
Register it on the builder:
src-tauri/src/lib.rs
init() reads its configuration from tauri.conf.json and validates it at startup. If you need to supply a custom WebAuthn ceremony provider, use PluginBuilder instead — see Passkeys.

The frontend packages

@exegia/use-auth is published to the public npm registry and installs with no extra configuration:
The bindings package is published there too, so installing it directly needs no registry mapping and no token either:
@exegia/plugin-supabase-auth is also published to GitHub Packages at the same version, for projects that already map the @exegia scope there. Both registries get every release, and the release pipeline verifies they agree before it tags. Nothing here requires that mapping — if you do use it, point the whole scope at GitHub Packages and give it a token with read:packages.
@exegia/use-auth declares react and react-dom 19 as peer dependencies and depends on the bindings package, so installing the hooks pulls the bindings in with it. It ships no stylesheet and no components — nothing to import besides the hooks themselves.

Next

Configuration

Point the plugin at your project and tune persistence, refresh, and OAuth ports.