IncomingMessage data event
The 'data' event is emitted with a chunk parameter of type Buffer containing a chunk of response body data. The data event is the usual method of transferring response data into applicative code.
incomingmessage/events
8 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
IncomingMessage end event
The 'end' event is emitted when the response body has ended. It must be placed before the 'data' event.
IncomingMessage aborted event
The 'aborted' event is emitted when a request has been canceled during an ongoing HTTP transaction.
IncomingMessage error event
The 'error' event is emitted when an error was encountered while streaming response data events. It returns an error parameter of type Error that typically holds an error string identifying the failure root cause. For example, if the server closes the underlying connection while the response is still streaming, an error event will be emitted on the response object and a close event will subsequently follow on the request object.
IpcMainServiceWorkerEvent reply method signature
The reply method on IpcMainServiceWorkerEvent accepts a channel parameter (string) and variadic args parameter (any[]), and will send an IPC message to the renderer frame that sent the original message being handled.
IpcRendererEvent structure
IpcRendererEvent extends Event. It has two properties: sender (IpcRenderer instance that emitted the event) and ports (array of MessagePorts transferred with the message).
IpcRendererEvent.sender property
The sender property of IpcRendererEvent is an IpcRenderer instance that emitted the event originally.
IpcRendererEvent.ports property
The ports property of IpcRendererEvent is a list (array) of MessagePorts that were transferred with the message.