add-ipc-surface

To implement an Electron IPC surface, you must define a clear contract with a JSON-safe data shape, place API interfaces correctly, and handle logic across main and preload sides. This ensures reliable cross-process communication.

Maintaining IPC contract parity requires a structured process for defining data shapes and managing logic across main, preload, and renderer sides. This approach ensures consistent communication and prevents boundary issues.

Electron IPC logic requires implementing handlers on the main side and exposing safe interfaces on the preload side. Proper placement of these API interfaces avoids common pitfalls and ensures secure renderer interaction.

You need a JSON-safe data shape for an IPC contract whenever passing complex objects between Electron processes. Defining this shape explicitly maintains contract parity and ensures reliable cross-process serialization.

Yes, this approach works with existing Electron applications by snapshotting the current IPC contract. You can then follow the outlined steps to extend or add new IPC surfaces while maintaining secure communication.

Boundary issues occur when API interfaces are misplaced between Electron processes. Following structured guidance for interface placement avoids these pitfalls and ensures the renderer interacts securely with the IPC surface.