Emitted when the stream and any of its underlying resources (a file descriptor, for example) have been closed.
Emitted when the stream and any of its underlying resources (a file descriptor, for example) have been closed. The event indicates that no more events will be emitted, and no further computation will occur.
Attaching a 'data' event listener to a stream that has not been explicitly paused will switch the stream into flowing mode.
Attaching a 'data' event listener to a stream that has not been explicitly paused will switch the stream into flowing mode. Data will then be passed as soon as it is available.
This event fires when there will be no more data to read.
This event fires when there will be no more data to read. Note that the 'end' event will not fire unless the data is completely consumed. This can be done by switching into flowing mode, or by calling stream.read() repeatedly until you get to the end.
Emitted if there was an error when writing or piping data.
Emitted if there was an error when writing or piping data.
When a chunk of data can be read from the stream, it will emit a 'readable' event.
When a chunk of data can be read from the stream, it will emit a 'readable' event. In some cases, listening for a 'readable' event will cause some data to be read into the internal buffer from the underlying system, if it hadn't already.
Readable Events