[dbfx]

Lands the three Dependabot major upgrades that each fail CI on their own, as one change. They interact (Forge's Vite plugin, the Vite version and the Tailwind build integration), so they are done together.

Supersedes

• chore(deps): bump postcss-selector-parser and tailwindcss #30 – Tailwind CSS 3.4 → 4.3.3 (and postcss-selector-parser, which is no longer in the tree at all)
• chore(deps-dev): bump vite from 5.4.21 to 8.3.4 #33 – Vite 5.4.21 → 8.3.4
• chore(deps): bump tar, @electron-forge/cli, @electron-forge/maker-squirrel, @electron-forge/maker-zip, @electron-forge/plugin-auto-unpack-natives, @electron-forge/plugin-fuses and @electron-forge/plugin-vite #34 – Electron Forge 7.11.1 → 8.0.1 (cli, maker-squirrel, maker-zip, plugin-auto-unpack-natives, plugin-fuses, plugin-vite) and tar → 7.5.22

Those PRs are left open; close them once this merges.

What changed

Electron Forge 8

• @electron/fuses ^1.8.0 → ^2.1.3 (peer of plugin-fuses@8; this was the npm ci ERESOLVE in chore(deps): bump tar, @electron-forge/cli, @electron-forge/maker-squirrel, @electron-forge/maker-zip, @electron-forge/plugin-auto-unpack-natives, @electron-forge/plugin-fuses and @electron-forge/plugin-vite #34).
• Forge 8 requires Node >= 22.13: ci.yml and release.yml move from Node 20 to Node 22.
• plugin-vite@8 emits main.cjs / preload.cjs instead of .js: package.json main and the preload: path in src/main/main.ts are updated. Without this the app packages fine but starts without its preload API.
• tsconfig.json: module: ESNext + moduleResolution: bundler (type-check only) so the ESM-only Forge 8 / Vite 8 type declarations resolve.

Vite 8

• @vitejs/plugin-react ^4.3.4 → ^6.1.2 (v4 only peers Vite 4–7; this was the ERESOLVE in chore(deps-dev): bump vite from 5.4.21 to 8.3.4 #33). The config never used the removed babel option.
• vite.*.config.ts → vite.*.config.mts (and the references in forge.config.ts) so the configs load as native ESM.

Tailwind CSS 4

• Uses the @tailwindcss/vite plugin; postcss.config.js, autoprefixer and the direct postcss dependency are removed.
• tailwind.config.js is replaced by @theme in src/renderer/styles/globals.css (surface colours, Inter / JetBrains Mono font stacks, pulse-slow and glow animations, class-based dark variant).
• v3 defaults that v4 changed are pinned in globals.css: default border colour (gray-200), placeholder colour (gray-400), cursor: pointer on buttons, hover: applying unconditionally, and gradients interpolating in sRGB (bg-linear-to-*/srgb).
• Renamed utilities in components: flex-shrink-0 → shrink-0, outline-none → outline-hidden, bg-gradient-to-* → bg-linear-to-*/srgb.

package-lock.json was regenerated with npm 10 (Node 22). Every version change in it follows from the bumps above.

One intended visual difference

The status dot in the target input (status-dot-idle, -running, …) is now coloured. On main those classes are built dynamically (status-dot-${status}), so Tailwind 3 purged them and the dot rendered transparent. Tailwind 4 does not purge plain CSS in @layer components, so the dot now shows as the stylesheet always intended.

Tailwind 4's default palette is defined in OKLCH rather than hex, so palette colours can differ by an imperceptible amount.

Verified (Linux, Node 22.23 / npm 10.9)

• npm ci from a clean tree, npx tsc --noEmit, npm run package (the three CI steps).
• electron-forge make for the zip maker.
• Launched the packaged app headless: the window loads, the preload bridge (window.mtrApi) is present, and the start screen matches a main build in a side-by-side screenshot and computed-style check, apart from the status dot above.

Not verified

• Anything on Windows beyond what CI runs here (install, type-check, package).
• The Squirrel installer and the release.yml flow (npm run make, latest.yml generation, auto-update) under Forge 8.
• npm start dev server / HMR.
• Views other than the start screen (map, visual trace, loss monitor, alerts, about) were not compared visually.

🤖 Generated with Claude Code