github.com/Quramy/electron-connect @v0.6.3
Chat with this repoWhat it actually does AI analysis from the code graph — generated when you open this
README
electron-connect 
Utility tool to develop applications with Electron.
Using this in your Node.js scripts (e.g. gulpfile.js), you can livereload your Electron app.
It provides the following features:
- start (and restart) Electron application.
- reload renderer processes.
- stop Electron application.
Install
Use npm:
npm install electron
npm install electron-connect --save-dev
Usage
electron-connect has server and client components. They communicate with each other using WebSocket.
The server component manages Electron process and broadcasts reload event to client, and client components reload renderer's resources.
Server
Here is an example creating a server in gulpfile.
'use strict';
var gulp = require('gulp');
var electron = require('electron-connect').server.create();
gulp.task('serve', function () {
// Start browser process
electron.start();
// Restart browser process
gulp.watch('app.js', electron.restart);
// Reload renderer process
gulp.watch(['index.js', 'index.html'], electron.reload);
});
Client
A client can be created in either browser process or renderer process.
Note: Please make sure it is not done in both.
- RendererProcess
<html>
<body>
<script>require('electron-connect').client.create()</script>
</body>
</html>
Do you want to use this tool for only develop environment ?
You can remove the <script> block in your gulpfile using gulp-useref.
- BrowserProcess
'use strict';
var app = require('app');
var BrowserWindow = require('browser-window');
var client = require('electron-connect').client;
app.on('ready', function () {
var mainWindow = new BrowserWindow({
width: 400,
height: 300
});
mainWindow.loadUrl('file://' + __dirname + '/index.html');
// Connect to server process
client.create(mainWindow);
});
If you want details, see example/simple.
API References
server.create([options])
optionsObjectelectronObject. Anelectronmodule. Set it If you want to use your forked Electron.useGlobalElectronBoolean. If set, electron-connect useselectronmodule installed globally (default:false).pathString. A path to yourpackage.jsonfile (default:process.cwd()).portNumber. WebSocket server port (default:30080).spawnOptObject. Options for spawn.logLevelNumber. The granularity of the electron-connect logging in your prompt.0- warning only,1- warning and info only,2- all logs (default:1).stopOnCloseBoolean. If set, closing last remaining window stops the electron application.
Returns a new ProcessManager object.
If neither electron nor useGlobalElectron option is set, electron-connect searches for electron module automatically.
- First, electron-connect searches
electroninstalled locally. - If not hit, electron-connect uses
electroninstalled globally.
New in version 0.5.x and onwards :
Now, ProcessManager's start(), restart() and stop() methods invoke callback with an argument that indicates the state of the electron process, which could be one of the following string values -
* started
* restarting
* restarted
* stopped
See example/stop-on-close, where you can find sample code that uses stopOnClose option and stopped state to shutdown gulp process gracefully.
Class: ProcessManager
start([args], [callback])
argsString or Array. Additional arguments used when create a process.callbackFunction
Starts a server and Electron application process.
restart([args], [callback])
argsString or Array. Additional arguments used when create a process.callbackFunction
Kills Electron process if it exsists, and starts new one.
This method is useful for callback of your browserProcess sourcecodes' change event.
reload([ids])
idsString or Array. A list of id of target client.
Emit reload event to target clients. Broadcasts reload event to all connected Client object if ids not set.
This method does not kill any Electron processes.
This method is useful for callback of your rendererProcess sourcecodes' change event.
stop([callback])
callbackFunction
Kills Electron process and stops server.
on(eventName, callback)
eventNameStringcallbackFunction
Registers an eventhandler that gets invoked when an event is emitted by Client.sendMessage.
broadcast(eventName, [data])
eventNameString. A message type.dataObject. A message data.
Broadcasts an event to all clients.
client.create([browserWindow], [options], [callback])
browserWindowObject. Optional, in rendererProcess only. Required, when client is created in browserProcess.optionsObjectportNumber. WebSocket server port (default:30080) that client should connect to.sendBoundsBooleanlogLevelNumber. See server.create([options]).logLevel.callbackFunction
Creates a new Client object associated with browserWindow and connects to ProcessManager.
The browserWindow should be an Electron browser-window instance.
Once a client is created and connected to the server, client can receive events (e.g. reload).
If sendBounds is set (default true), client sends a bounds object when browserWindow moves or resizes.
And when ProcessManager.restart() is called, client recovers the bounds stored at server.
Class: Client
id
An identifier of this client. It is a same value browserWindow.id.
on(eventName, callback)
eventNameStringcallbackFunction
Registers an eventhandler that gets invoked, when an event is emitted by ProcessManager.broadcast.
sendMessage(eventName, [data])
eventNameString. A message type.dataObject. A message data.
Emits an event to ProcessManager.
License
MIT
Core symbols most depended-on inside this repo
createWindowOneShape
Languages
Modules by API surface
Used by 1 indexed graphs manifest dependencies, hub-wide
For agents
$ claude mcp add electron-connect \
-- python -m otcore.mcp_server <graph>