Tauri (Vanilla) + Elm based counter example, where the counter is incremented via Tauri's Rust backend, decremented via WebAssembly, and reset via Elm.
 
 
 
Go to file
eaon e8a22bb163
Switch from make to just, update Tauri and add Cargo.lock files
2023-05-15 19:08:35 -04:00
.vscode Initial commit 2023-04-07 21:25:41 -04:00
public Use JS Number in WASM rather than BigInt in JS 2023-04-11 09:28:23 -04:00
src-elm More consistent folder naming and building infrastructure 2023-04-11 09:50:55 -04:00
src-tauri Switch from make to just, update Tauri and add Cargo.lock files 2023-05-15 19:08:35 -04:00
src-wasm Switch from make to just, update Tauri and add Cargo.lock files 2023-05-15 19:08:35 -04:00
.gitignore Move decrement function to a WebAssembly module 2023-04-08 23:07:27 -04:00
Justfile Switch from make to just, update Tauri and add Cargo.lock files 2023-05-15 19:08:35 -04:00
LICENSE Add license 2023-04-07 21:33:37 -04:00
README.md Switch from make to just, update Tauri and add Cargo.lock files 2023-05-15 19:08:35 -04:00
elm.json More consistent folder naming and building infrastructure 2023-04-11 09:50:55 -04:00

README.md

Tauri (Vanilla) + Elm Counter Example

This is a quick and dirty proof-of-concept for passing messages from Tauri's Rust backend as well as a WebAssembly module to Elm's frontend (and vice versa) without relying on the typical JavaScript ecosystem.

In this project, the counter is incremented via Tauri's Rust backend, decremented via WebAssembly, and reset via Elm.

Dependencies

  • Rust (… yes)
  • Elm 0.19.1 binary in your PATH
  • wasm-pack (i.e. cargo install wasm-pack)
  • create-tauri-app (i.e. cargo install create-tauri-app)
  • just (i.e. cargo install just)

Building

cargo-tauri dev