v1.0.37
v1.0.37 — Hotfix (June 26, 2026)
Fixed Dashboard crash on null status
When /api/server/status returns a 500 error, the Dashboard no longer crashes with Cannot read properties of null (reading 'onlinePlayers'). Added a null-status guard that shows "Unable to connect to server. Retrying..." instead of crashing. All null guards changed from !== null (which fails for undefined when ?. returns undefined) to != null (which catches both null and undefined).
Fixed production package.json path resolution
The /api/server/status endpoint used require('../../package.json') which resolves to dist/package.json in the production ASAR bundle, causing a 500 error. Added a try-catch fallback chain that works in both development (tsx watch) and production (Electron ASAR) environments.
Null-safe Dashboard rendering
All computed values (cpuPercent, ramPercent, sysRamPercent, diskPercent) now use optional chaining with ?? fallbacks, so they never crash when status is null or partially initialized.