Electron eRPC
Implements type-safe communication between Electron processes using eRPC and tRPC patterns.
The erpc skill streamlines the implementation of type-safe Inter-Process Communication (IPC) within Electron applications. By leveraging eRPC and tRPC-inspired patterns, it enables developers to maintain end-to-end type safety between the main process, preload scripts, and renderer clients. This skill enforces architectural best practices, such as separating business logic into services, validating IPC boundaries as API endpoints, and utilizing shared types to prevent process-specific leaks, ensuring a robust and maintainable desktop application architecture.
Key Features
01Type-safe renderer clients using ipcLink
02Main-process router and service layer separation
03Preload bridge generation with exposeElectronTRPC
04Input and output validation for IPC boundaries
05End-to-end type safety across Electron processes
06780 GitHub stars
Use Cases
01Adding new feature routes to an Electron main-process router
02Refactoring untyped Electron IPC calls to a type-safe tRPC pattern
03Exposing backend services to the frontend renderer via preload scripts