ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #electron
A decision guide for Atom package developers on choosing between the Command Palette and Spacebar API for action discovery and execution speed.
Electron's contextIsolation feature separates Node.js and DOM contexts, preventing renderer code from accessing Node APIs directly and mitigating XSS and prototype pollution attacks.
Learn how to use a single Quasar CLI project to target SPA, SSR, PWA, and Electron, reducing code duplication while managing platform-specific constraints.
A practical look at using contextIsolation, preload scripts, and contextBridge to keep Electron renderer processes from accessing Node.js directly.
Expose a limited API from Electron's preload script to the renderer with contextBridge, keeping Node integration disabled.
Isolate Electron renderer processes with contextIsolation, nodeIntegration, and a typed preload API; validate all IPC in the main process.
Renderer code calling window.myAPI gets undefined even though the preload script exposes it. This guide shows how to isolate the cause and fix it without weakening renderer security.
Prevent renderer code in Electron from accessing Node APIs by enabling contextIsolation, disabling nodeIntegration, and exposing a safe API via a preload script. This guide shows the minimal config, trust boundaries, checks, and failure modes.
Electron's contextBridge lets you expose a narrow, audited API from the main process to the renderer. Here is how to replace nodeIntegration with an explicit IPC contract, with a worked file-read example.
javascript
quasar