A fork of https://github.com/JonasKruckenberg/tauri-sys that builds for my choices of features
e28a0bb749
* feat: improve DX of events * Update global_shortcut.rs * Update event.rs * deploy docs to gh pages * Delete rustdoc.yml * add tests for global shortcut * improve logs produced by tauri_log * wip docs * update docs * move error to separate module * feat: simplify functions returning array backed iterators * rebase and cleanup * fixes |
||
|---|---|---|
| .github | ||
| examples/test | ||
| src | ||
| tauri@2e1bd04775 | ||
| tests | ||
| .gitignore | ||
| .gitmodules | ||
| .nojekyll | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE_APACHE-2.0 | ||
| LICENSE_MIT | ||
| package.json | ||
| pnpm-lock.yaml | ||
| README.md | ||
tauri-sys
Raw bindings to the Tauri API
for projects using wasm-bindgen
Installation
This crate is not yet published to crates.io, so you need to use it from git. You also need a global installation of esbuild.
tauri-sys = { git = "https://github.com/JonasKruckenberg/tauri-sys" }
Usage
use serde::{Deserialize, Serialize};
use tauri_sys::tauri;
#[derive(Serialize, Deserialize)]
struct GreetArgs<'a> {
name: &'a str,
}
fn main() {
wasm_bindgen_futures::spawn_local(async move {
let new_msg: String = tauri::invoke("greet", &GreetArgs { name: &name.get() }).await.unwrap();
println!("{}", new_msg);
});
}
Features
All modules are gated by accordingly named Cargo features. It is recommended you keep this synced with the features enabled in your Tauri Allowlist but no automated tool for this exists (yet).
- all: Enables all modules.
- app: Enables the
appmodule. - clipboard: Enables the
clipboardmodule. - dialog: Enables the
dialogmodule. - event: Enables the
eventmodule. - mocks: Enables the
mocksmodule. - tauri: Enables the
taurimodule.
Are we Tauri yet?
These API bindings are not completely on-par with @tauri-apps/api yet, but here is the current status-quo:
appcliclipboarddialogeventfsglobal_shortcuthttpmocksnotificationospathprocessshelltauriupdaterwindow
The current API also very closely mirrors the JS API even though that might not be the most ergonomic choice, ideas for improving the API with quality-of-life features beyond the regular JS API interface are very welcome.