nextjs-to-tauri

# Next.js 16 → Tauri 2 Desktop App ## Overview Wrap a **client-side** Next.js 16 (App Router) app in a thin Tauri 2 native shell. The React code is untouched; Tauri serves the static export from its embedded asset server. Build in GitHub Actions so no local Rust is needed. **Core principle:** Tauri loads the static export over its own asset protocol — which behaves differently from a real HTTP server. Most migration pain is path/routing resolution, not React. ## When to use - The app is (or can be) a **static export** (`output: "export"`) — diffing/formatting/calculator/viewer tools, no SSR-at-runtime needed. - You want a desktop/portable `.exe`, `.dmg`, `.AppImage`, optionally with auto-update. **Do NOT use when** the app needs a live Node server at runtime (real API routes, SSR, server actions). Tauri can bundle a sidecar server, but that's a different, heavier playbook. ## Procedure Do these in order. Copy-paste templates live in the supporting files. 1. **Verify latest versions first** (they drift — never trust the numbers in templates): - npm: `npm view @tauri-apps/cli version` (+ `plugin-opener`, `plugin-updater`) - crates: `curl -sA x https://crates.io/api/v1/crates/tauri | python -c "import sys,json;print(json.load(sys.stdin)['crate']['max_stable_version'])"` (repeat for each `tauri-plugin-*`) - actions: `gh api repos/actions/checkout/releases/latest --jq .tag_name` (+ `actions/setup-node`, `Swatinem/rust-cache`, `actions/upload-artifact`; `tauri-app...