enum abstract DuplexEvent<T>(Event<T>)
package js.node.stream
to Event<T>
import js.node.stream.Duplex
Writable streams are an abstraction for a destination to which data is written.
See also:
Variables
inlineread onlyClose:DuplexEvent<() ‑> Void> = "close"
The 'close' event is 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.
See also:
inlineread onlyData:DuplexEvent<Dynamic ‑> Void> = "data"
The 'data' event is emitted whenever the stream is relinquishing ownership of
a chunk of data to a consumer. This may occur whenever the stream is switched
in flowing mode by calling readable.pipe(), readable.resume(), or by
attaching a listener callback to the 'data' event. The 'data' event will
also be emitted whenever the readable.read() method is called and a chunk of
data is available to be returned.
See also:
inlineread onlyDrain:DuplexEvent<() ‑> Void> = "drain"
If a call to stream.write(chunk) returns false, the 'drain' event will be emitted
when it is appropriate to resume writing data to the stream.
See also:
inlineread onlyEnd:DuplexEvent<() ‑> Void> = "end"
The 'end' event is emitted when there is no more data to be consumed from
the stream.
See also:
inlineread onlyError:DuplexEvent<Error ‑> Void> = "error"
inlineread onlyFinish:DuplexEvent<() ‑> Void> = "finish"
The 'finish' event is emitted after the stream.end() method has been called,
and all data has been flushed to the underlying system.
See also:
inlineread onlyPause:DuplexEvent<() ‑> Void> = "pause"
The 'pause' event is emitted when stream.pause() is called
and readableFlowing is not false.
See also:
inlineread onlyPipe:DuplexEvent<IReadable ‑> Void> = "pipe"
The 'pipe' event is emitted when the stream.pipe() method is called on a readable stream,
adding this writable to its set of destinations.
See also:
inlineread onlyReadable:DuplexEvent<() ‑> Void> = "readable"
The 'readable' event is emitted when there is data available to be read from
the stream. In some cases, attaching a listener for the 'readable' event will
cause some amount of data to be read into an internal buffer.
See also:
inlineread onlyResume:DuplexEvent<() ‑> Void> = "resume"
The 'resume' event is emitted when stream.resume() is
called and readableFlowing is not true.
See also:
inlineread onlyUnpipe:DuplexEvent<IReadable ‑> Void> = "unpipe"
The 'unpipe' event is emitted when the stream.unpipe() method is called on a Readable stream,
removing this Writable from its set of destinations.
See also: