v3.4.1 — Chart Hotfix

[v3.4.1] – 2026-06-14 (The "Chart Hotfix" Edition)

Patch release fixing a production regression introduced by the Vite 8 / Rolldown deploy hotfix (#95): every chart tab threw a blank React error #130 and failed to render. Web app + desktop bumped 1.4.0 → 1.4.1; repo public-facing version 3.4.0 → 3.4.1.

🐛 Charts render again (React #130)

• EChart.tsx imported the chart wrapper from echarts-for-react/lib/core — the CommonJS build. Under Vite 8's Rolldown bundler the CJS default-interop wraps module.exports = class into a namespace object, so <ReactEChartsCore/> received an object instead of a component → React error #130 on every chart page (all pages/charts/* + the Dashboard). Switched the import to the ESM build echarts-for-react/esm/core, which has a clean export default. echarts core and echarts-wordcloud were already ESM, so this single import was the only offender.
• Verified at runtime against the production (Rolldown) build (the step skipped in #95): bar, pie/donut, line, treemap, heatmap and wordcloud charts all render with zero console errors. echarts/openpgp remain lazy async chunks (not eager-preloaded in index.html).

⚠️ glib advisory (Linux desktop) — acknowledged, no upstream fix

• The Dependabot alert for the glib crate (GHSA-wrw7-89jp-8q8g, medium, Linux-only) cannot be resolved within Tauri 2.x: the latest webkit2gtk crate (2.0.2) pins glib ^0.18, tao/wry pin gtk ^0.18, and Tauri 3 is not released. Only the Linux build links glib (Windows = WebView2, macOS = Cocoa) and the app does not call the affected API, so the alert is dismissed as tolerable risk. Will revisit when the upstream stack adopts gtk-rs 0.20. See TAURI.md.