electron/docs/api/ipc-main.md

159 lines
4.8 KiB
Markdown
Raw Normal View History

2015-11-10 08:48:24 +00:00
# ipcMain
2016-04-21 22:39:12 +00:00
> Communicate asynchronously from the main process to renderer processes.
2016-11-23 19:20:56 +00:00
Process: [Main](../glossary.md#main-process)
2016-11-03 17:26:00 +00:00
The `ipcMain` module is an [Event Emitter][event-emitter]. When used in the main
process, it handles asynchronous and synchronous messages sent from a renderer
process (web page). Messages sent from a renderer will be emitted to this
module.
2015-11-10 08:48:24 +00:00
## Sending Messages
It is also possible to send messages from the main process to the renderer
2016-02-16 03:34:39 +00:00
process, see [webContents.send][web-contents-send] for more information.
2015-11-10 08:48:24 +00:00
* When sending a message, the event name is the `channel`.
* To reply to a synchronous message, you need to set `event.returnValue`.
* To send an asynchronous message back to the sender, you can use
`event.reply(...)`. This helper method will automatically handle messages
coming from frames that aren't the main frame (e.g. iframes) whereas
`event.sender.send(...)` will always send to the main frame.
2015-11-10 08:48:24 +00:00
An example of sending and handling messages between the render and main
processes:
```javascript
// In main process.
2018-09-13 16:10:51 +00:00
const { ipcMain } = require('electron')
ipcMain.on('asynchronous-message', (event, arg) => {
2017-11-29 10:58:24 +00:00
console.log(arg) // prints "ping"
event.reply('asynchronous-reply', 'pong')
})
2015-11-10 08:48:24 +00:00
ipcMain.on('synchronous-message', (event, arg) => {
2017-11-29 10:58:24 +00:00
console.log(arg) // prints "ping"
event.returnValue = 'pong'
})
2015-11-10 08:48:24 +00:00
```
```javascript
// In renderer process (web page).
// NB. Electron APIs are only accessible from preload, unless contextIsolation is disabled.
// See https://www.electronjs.org/docs/tutorial/process-model#preload-scripts for more details.
2018-09-13 16:10:51 +00:00
const { ipcRenderer } = require('electron')
console.log(ipcRenderer.sendSync('synchronous-message', 'ping')) // prints "pong"
2015-11-10 08:48:24 +00:00
ipcRenderer.on('asynchronous-reply', (event, arg) => {
console.log(arg) // prints "pong"
})
ipcRenderer.send('asynchronous-message', 'ping')
2015-11-10 08:48:24 +00:00
```
## Methods
2015-11-10 08:48:24 +00:00
The `ipcMain` module has the following method to listen for events:
2016-02-16 03:34:39 +00:00
### `ipcMain.on(channel, listener)`
2015-11-10 08:48:24 +00:00
* `channel` string
2016-02-16 03:34:39 +00:00
* `listener` Function
* `event` IpcMainEvent
* `...args` any[]
2015-11-10 08:48:24 +00:00
2016-02-16 03:34:39 +00:00
Listens to `channel`, when a new message arrives `listener` would be called with
`listener(event, args...)`.
2016-02-16 03:34:39 +00:00
### `ipcMain.once(channel, listener)`
* `channel` string
2016-02-16 03:34:39 +00:00
* `listener` Function
* `event` IpcMainEvent
* `...args` any[]
2016-02-16 03:34:39 +00:00
Adds a one time `listener` function for the event. This `listener` is invoked
only the next time a message is sent to `channel`, after which it is removed.
2016-02-16 03:34:39 +00:00
### `ipcMain.removeListener(channel, listener)`
* `channel` string
2016-02-16 03:34:39 +00:00
* `listener` Function
* `...args` any[]
2016-02-16 03:34:39 +00:00
Removes the specified `listener` from the listener array for the specified
`channel`.
2016-02-16 03:34:39 +00:00
### `ipcMain.removeAllListeners([channel])`
* `channel` string (optional)
Removes listeners of the specified `channel`.
2016-02-16 03:34:39 +00:00
### `ipcMain.handle(channel, listener)`
* `channel` string
* `listener` Function<Promise\<void> | any>
* `event` IpcMainInvokeEvent
* `...args` any[]
Adds a handler for an `invoke`able IPC. This handler will be called whenever a
renderer calls `ipcRenderer.invoke(channel, ...args)`.
If `listener` returns a Promise, the eventual result of the promise will be
returned as a reply to the remote caller. Otherwise, the return value of the
listener will be used as the value of the reply.
```js
// Main process
ipcMain.handle('my-invokable-ipc', async (event, ...args) => {
const result = await somePromise(...args)
return result
})
// Renderer process
async () => {
const result = await ipcRenderer.invoke('my-invokable-ipc', arg1, arg2)
// ...
}
```
The `event` that is passed as the first argument to the handler is the same as
that passed to a regular event listener. It includes information about which
WebContents is the source of the invoke request.
Errors thrown through `handle` in the main process are not transparent as they
are serialized and only the `message` property from the original error is
provided to the renderer process. Please refer to
[#24427](https://github.com/electron/electron/issues/24427) for details.
### `ipcMain.handleOnce(channel, listener)`
* `channel` string
* `listener` Function<Promise\<void> | any>
* `event` IpcMainInvokeEvent
* `...args` any[]
Handles a single `invoke`able IPC message, then removes the listener. See
`ipcMain.handle(channel, listener)`.
### `ipcMain.removeHandler(channel)`
* `channel` string
Removes any handler for `channel`, if present.
## IpcMainEvent object
2015-11-10 08:48:24 +00:00
The documentation for the `event` object passed to the `callback` can be found
in the [`ipc-main-event`](structures/ipc-main-event.md) structure docs.
## IpcMainInvokeEvent object
The documentation for the `event` object passed to `handle` callbacks can be
found in the [`ipc-main-invoke-event`](structures/ipc-main-invoke-event.md)
structure docs.
[event-emitter]: https://nodejs.org/api/events.html#events_class_eventemitter
[web-contents-send]: web-contents.md#contentssendchannel-args