How luckjiawei/frpc-desktop works
Project type and purpose
• This is a cross-platform desktop application built with Electron.
• The renderer (frontend) is a Vue/Vite single‐page app providing a GUI for configuring and controlling FRP (Fast Reverse Proxy) clients.
• The main (backend) is an Electron Node process organizing controllers, services, repositories, and spawning FRP processes.
High-level architecture components
a. Renderer Process (UI Layer)
• Folder: /src – Vue components, views, router, store (Vuex), assets, styles
• Responsibilities: display pages (launch, proxy list, download, config, logger, about), send user commands via IPC
b. Preload Script (IPC Bridge)
• File: electron/preload/index.ts
• Exposes a safe API (ipcRenderer) to the renderer for requests like “start proxy,” “fetch config,” “download FRP.”
c. Main Process (Application Layer)
• Entry: electron/main/index.ts
• Controllers (electron/controller/*.ts): handle IPC events, route them to services
• IpcRouter (electron/core/IpcRouter.ts): central router for mapping IPC channels to controller methods
• Services (electron/service/*.ts): core business logic – FRPC process management, GitHub downloads, logging, system info
• Repositories (electron/repository/*.ts): file-based persistence of configs, versions, proxies
• Core & DI (electron/core/BeanFactory.ts + annotations): component management, dependency injection, global constants, error types
• Utils (electron/utils): file, path, security, response formatting, ID generation
d. External Processes & Services
• FRP client process (spawned by FrpcProcessService)
• GitHub API & mirror sites for downloading FRP releases
• Local file system for storing JSON configs & logs
• Python script (electron/json/extract.py) for preprocessing JSON data
e. Public Static & Configuration
• electron-builder.json5 – packaging config
• Vite, Tailwind, TypeScript configs