⏱️ Fast dev • 🧩 Import maps • 📦 Embed folder

TauriKargo — code fast, see fast, package fast

A flow that favors an ultra-short iterative loop: TypeScript transpiled on the fly, JS libraries imported from node_modules via an import map, and packaging that embeds a folder (front + optional backend).

Direct TypeScript Import map → node_modules Embedded backend (Python/Node/Deno/Bun)

⬇️ Download TauriKargo.zip (Windows) ⬇️ Download TauriKargoExamples.zip (Windows) 📚 API Reference

Embedded backend diagram

Frontend (WebView) index.html + /src TS + import map fetch → http://127.0.0.1:PORT/api/* Local HTTP TauriKargo executable • launches WebView • spawns backend (if present) spawn Backend Python Node Deno Bun

The backend listens locally (127.0.0.1:PORT). The front calls the API routes. You embed what you want (binary or script + runtime).

Why faster than Electron?

  • No heavy runtime to embed (Chromium+Node): uses the native WebView.
  • No mandatory bundling for development: TS transpiled on the fly, import map to node_modules.
  • Simple packaging: one executable + one embedded folder.

Why faster than native Tauri?

  • Very short dev loop: no Rust rebuild at every UI iteration.
  • Zero mandatory “dist”: write TS, see the result immediately.
  • Backend option: if needed, spawn local 127.0.0.1 without friction.

When to prefer Electron/native Tauri?

  • Very deep OS integrations (advanced system APIs, drivers, sandbox…)
  • Extreme GPU/CPU performance where a dedicated Rust/WebGPU pipeline is required.
  • Specific IT policies (signing, binary hardening, etc.).