Context Isolation transition to contextBridge for secure API exposure

Electron version 12 and later default to contextIsolation: true to prevent renderer processes from accessing Node.js internals. This security boundary is designed to stop unauthorized public access to system APIs by separating the JavaScript contexts of the preload script and the renderer.

While contextBridge allows the definition of a controlled gateway for specific functions, there is a technical trade-off between the security of serialized communication and the performance overhead introduced when passing large data structures across the bridge.

• What are the performance implications of high-frequency data serialization across the contextBridge compared to shared state?
• Are there documented patterns to minimize latency when exposing complex system APIs without compromising the isolation boundary?