ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #electron
Learn how Electron’s context isolation feature prevents renderer code from accessing Node.js APIs directly and how to expose only the functions you need via contextBridge.
Learn how to lock down Electron renderer processes by enabling contextIsolation, disabling nodeIntegration, and exposing a minimal API via a preload script. This guide covers requirements, design, trust boundaries, operational checks, failure modes, and when the design must change.
Learn how to implement the Context Bridge pattern in Electron to isolate your renderer process and prevent XSS-based system access.
Explore how Atom's 'everything is a package' architecture removed the bottleneck of core development by treating every feature as a modular JavaScript extension.
An architecture note on Electron's main/renderer split: the smallest preload bridge, validating IPC payloads in the main process, navigation lockdown, and the checks that prove the boundary holds.
Learn how to secure Electron applications using ContextBridge and the ipcRenderer.invoke pattern to prevent RCE vulnerabilities while maintaining a clean API.
When an Electron application uses a persistent session (e.g., session.fromPartition('persist:auth') ) to store authentication cookies or tokens, the framework will automatically send those credentials with outgoing requests unless a custom handler intervenes. If the stored credentials have expired, the app may still leak them to servers, violating least‑priv
Developers using Algolia's official JavaScript search client version 4 need to confirm whether the library honors custom certificate authority configurations when operating inside Electron or React Native wrappers. The v4 release enabled strict TLS verification by default and removed the previous fallback that tolerated self‑signed certificates, but the publ
VSCodium is built from the MIT-licensed VS Code source but strips proprietary branding and telemetry. This process modifies the internal product identifier used by the application to identify itself to extensions. Certain extensions are hard-coded to target the vscode product ID. When these extensions are installed via the Open VSX Registry, they may fail to
javascript
vscodium