electron/docs/api/structures/ipc-renderer-event.md

# IpcRendererEvent Object extends `Event`

* `sender` [IpcRenderer](../ipc-renderer.md) - The `IpcRenderer` instance that emitted the event originally
* `senderId` Integer - The `webContents.id` that sent the message, you can call `event.sender.sendTo(event.senderId, ...)` to reply to the message, see [ipcRenderer.sendTo][ipc-renderer-sendto] for more information. This only applies to messages sent from a different renderer. Messages sent directly from the main process set `event.senderId` to `0`.
* `senderIsMainFrame` boolean (optional) - Whether the message sent via [ipcRenderer.sendTo][ipc-renderer-sendto] was sent by the main frame. This is relevant when `nodeIntegrationInSubFrames` is enabled in the originating `webContents`.
* `ports` [MessagePort][][] - A list of MessagePorts that were transferred with this message

[ipc-renderer-sendto]: ../ipc-renderer.md#ipcrenderersendtowebcontentsid-channel-args-deprecated
[MessagePort]: https://developer.mozilla.org/en-US/docs/Web/API/MessagePort
refactor: Split 'Event' docs/types into more specific Event types (#17038) * Event = Base event type (with preventDefault) * IpcMainEvent = Event that ipcMain emits (with sender, reply, etc.) * IpcRendererEvent = Event that ipcRenderer emits (with sender, senderId, etc.) * KeyboardEvent = Event that we emit with keyboard flags (ctrlKey, altKey, etc.) This will dramatically improve peoples TS experience with IPC events 2019-02-19 09:24:19 +00:00			# IpcRendererEvent Object extends `Event`

docs: add links to IPC event structures (#37760) 2023-03-30 17:13:21 +00:00			* `sender` [IpcRenderer](../ipc-renderer.md) - The `IpcRenderer` instance that emitted the event originally
refactor: Split 'Event' docs/types into more specific Event types (#17038) * Event = Base event type (with preventDefault) * IpcMainEvent = Event that ipcMain emits (with sender, reply, etc.) * IpcRendererEvent = Event that ipcRenderer emits (with sender, senderId, etc.) * KeyboardEvent = Event that we emit with keyboard flags (ctrlKey, altKey, etc.) This will dramatically improve peoples TS experience with IPC events 2019-02-19 09:24:19 +00:00			* `senderId` Integer - The `webContents.id` that sent the message, you can call `event.sender.sendTo(event.senderId, ...)` to reply to the message, see [ipcRenderer.sendTo][ipc-renderer-sendto] for more information. This only applies to messages sent from a different renderer. Messages sent directly from the main process set `event.senderId` to `0`.
feat: add `senderIsMainFrame` to messages sent via `ipcRenderer.sendTo()` (#38868) * feat: add isMainFrame to events emitted via ipcRenderer.sendTo() * chore: rename isMainFrame to senderIsMainFrame 2023-07-24 12:27:30 +00:00			* `senderIsMainFrame` boolean (optional) - Whether the message sent via [ipcRenderer.sendTo][ipc-renderer-sendto] was sent by the main frame. This is relevant when `nodeIntegrationInSubFrames` is enabled in the originating `webContents`.
docs: add links to IPC event structures (#37760) 2023-03-30 17:13:21 +00:00			* `ports` [MessagePort][][] - A list of MessagePorts that were transferred with this message
refactor: Split 'Event' docs/types into more specific Event types (#17038) * Event = Base event type (with preventDefault) * IpcMainEvent = Event that ipcMain emits (with sender, reply, etc.) * IpcRendererEvent = Event that ipcRenderer emits (with sender, senderId, etc.) * KeyboardEvent = Event that we emit with keyboard flags (ctrlKey, altKey, etc.) This will dramatically improve peoples TS experience with IPC events 2019-02-19 09:24:19 +00:00
feat: deprecate `ipcRenderer.sendTo()` (#39091) * feat: deprecate ipcRenderer.sendTo() * docs: add _Deprecated_ to ipcRenderer.sendTo() 2023-07-21 09:16:44 +00:00			`[ipc-renderer-sendto]: ../ipc-renderer.md#ipcrenderersendtowebcontentsid-channel-args-deprecated`
docs: add links to IPC event structures (#37760) 2023-03-30 17:13:21 +00:00			`[MessagePort]: https://developer.mozilla.org/en-US/docs/Web/API/MessagePort`