nextjs-to-electronlisted

# Next.js → Electron Desktop App ## Overview Wrap a **client-side** Next.js (App Router) static export in a thin Electron shell. Electron bundles its own Chromium, so unlike Tauri it needs **no system WebView2** — the reason to pick it for locked-down/intranet machines. The React code stays **untouched**; all desktop behavior lives in a `electron/` main-process layer that serves the static export. **Core principle:** Serve the export over a custom `app://` protocol, NOT `file://`. Almost all migration pain is path/origin resolution, not React — and `file://` silently breaks both. (See [electron-files.md](electron-files.md) for all copy-paste code.) ## When to use - The app is (or can be) a **static export** (`output: "export"`) — diff/format/calculator/viewer tools, no SSR or API-at-runtime. - You want a Windows desktop build that runs **fully offline**, especially where WebView2 is absent (LTSC/Server images, air-gapped intranet) so Tauri won't launch. **Target current Electron and check the floor first.** Electron follows Chromium, so "old machine" has a hard bottom: **64-bit Windows 10 or newer**. Windows 7/8/8.1 were dropped years ago, and **Electron 44 stopped publishing 32-bit Windows (`ia32`) binaries altogether** — v43.5.1 ships 7 `win32-ia32` release assets, v44.0.0 ships none. A 32-bit or pre-10 target is out of scope for this playbook; do not plan around pinning an old Electron to reach it, because that lands you on an unsupported build with no security updat