ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #electron
Learn how Electron’s context isolation and contextBridge let you expose safe, limited APIs from the preload script to the renderer, keeping Node access locked down.
Explore how Atom's Electron-based architecture allows for deep extensibility via Node.js, and learn how to implement custom commands using the Package system.
Explore the engineering behind Atom's 'hackable' architecture, the use of Electron for IDE composability, and the performance trade-offs of a JS-driven UI.
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.
nodejs
javascript