fix(desktop): Windows native modules — registry-js via N-API prebuild + defensive loading #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/desktop-native-modules"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes the Windows crash
registry.node is not a valid Win32 application(Wine cross-build on the Linux runner packaged Linux-compiled native .node addons into the Windows app).B (CI) — registry-js works with NO Windows runner: registry-js ships ABI-independent N-API prebuilds (
registry-js-v1.16.1-napi-v3-win32-x64.tar.gz), which load on Electron 41. CI now fetches that (verified:PE32+ executable ... x86-64) and packages it;--config.npmRebuild=falsestops electron-builder re-clobbering it. So GPO/MDM policy + Windows light/dark detection work on Windows.C (resilience): all 4 native modules (registry-js, cf-prefs, windows-focus-assist, macos-notification-state) load lazily + guarded, so a missing/wrong-arch .node disables that one feature instead of crashing the main process. Fixes latent cross-platform crashes too (cf-prefs/macos-* were imported at module scope, fail to load on Windows).
Remaining gap:
windows-focus-assistpublishes no prebuilds and needs MSVC — it stays disabled via the guards (only Focus-Assist DND detection lost). A Windows build runner (#12) is now optional, needed only for that one minor feature.Branding gate passes. Windows CI job builds green.
fix(desktop): Windows native modules (win32 prebuilds) + defensive loadingto fix(desktop): defensive native-module loading — stop the Windows startup crashfix(desktop): defensive native-module loading — stop the Windows startup crashto fix(desktop): Windows native modules — registry-js via N-API prebuild + defensive loading