26 lines
855 B
Markdown
26 lines
855 B
Markdown
# @mizan/tauri-transport
|
|
|
|
Mizan transport adapter routing calls through Tauri's IPC instead of
|
|
HTTP fetch. Paired with the `mizan-tauri` Rust plugin.
|
|
|
|
```bash
|
|
npm install @mizan/base @mizan/tauri-transport @tauri-apps/api
|
|
```
|
|
|
|
```ts
|
|
import { configure } from "@mizan/base";
|
|
import { tauriTransport } from "@mizan/tauri-transport";
|
|
|
|
configure({ transport: tauriTransport() });
|
|
```
|
|
|
|
That's the entire surface — no other API. Once configured at the app
|
|
entry (top of `main.tsx`), every `mizanCall` / `mizanFetch` in the
|
|
generated client routes through `invoke('plugin:mizan|mizan_invoke',
|
|
{ envelope })` instead of `fetch()`. Codegen output (Stage 1 + Stage 2
|
|
React hooks) is unchanged from the HTTP case; only the wire channel
|
|
differs.
|
|
|
|
See `backends/mizan-tauri/README.md` for the Rust-side plugin setup,
|
|
envelope shape, and full end-to-end walkthrough.
|