f5d70476f0
cargo build --release alone doesn't produce a working standalone binary in Tauri v2 — embedding the frontend vs. hitting devUrl at runtime is gated by the tauri/custom-protocol Cargo feature, not the debug/release profile. The scaffold never declared it, so even release builds tried to connect to localhost:1420. Added the standard default-on custom-protocol feature (cargo tauri dev strips it via --no-default-features for dev builds); a plain `cargo build --release --locked` in src/ now produces a real standalone binary with no dev-server dependency. Also fixes vite.config.js's file-watch ignore pattern, left stale by the src-tauri -> src rename: a bare "**/src/**" glob would have also matched frontend/src itself, so it's now an absolute path scoped to the Rust project dir specifically. |
||
|---|---|---|
| .. | ||
| src | ||
| static | ||
| .gitignore | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| svelte.config.js | ||
| tsconfig.json | ||
| vite.config.js | ||
Tauri + SvelteKit + TypeScript
This template should help get you started developing with Tauri, SvelteKit and TypeScript in Vite.
Recommended IDE Setup
VS Code + Svelte + Tauri + rust-analyzer.