PassThrough
The stream.PassThrough
class is a trivial implementation of a Transform
stream that simply passes the input bytes across to the output. Its purpose is
primarily for examples and testing, but there are some use cases wherestream.PassThrough
is useful as a building block for novel sorts of streams.
Properties
allowHalfOpen
booleanRequiredfalse
then the stream will automatically end the writable side when the readable side ends. Set initially by the allowHalfOpen
constructor option, which defaults to true
. This can be changed manually to change the half-open behavior of an existingDuplex
stream instance, but must be changed before the 'end'
event is emitted.closed
booleanRequiredtrue
after 'close'
has been emitted.destroyed
booleanRequiredtrue
after readable.destroy()
has been called.readable
booleanRequiredtrue
if it is safe to call readable.read()
, which means the stream has not been destroyed or emitted 'error'
or 'end'
.readableAborted
booleanRequired'end'
.readableDidRead
booleanRequired'data'
has been emitted.encoding
of a given Readable
stream. The encoding
property can be set using the readable.setEncoding()
method.readableEnded
booleanRequiredtrue
when 'end'
event is emitted.readableFlowing
null | booleanRequiredReadable
stream as described in the Three states
section.readableHighWaterMark
numberRequiredhighWaterMark
passed when creating this Readable
.readableLength
numberRequiredhighWaterMark
.readableObjectMode
booleanRequiredobjectMode
of a given Readable
stream.writable
booleanRequiredtrue
if it is safe to call writable.write()
, which means the stream has not been destroyed, errored, or ended.writableCorked
numberRequiredwritable.uncork()
needs to be called in order to fully uncork the stream.writableEnded
booleanRequiredtrue
after writable.end()
has been called. This property does not indicate whether the data has been flushed, for this use writable.writableFinished
instead.writableFinished
booleanRequiredtrue
immediately before the 'finish'
event is emitted.writableHighWaterMark
numberRequiredhighWaterMark
passed when creating this Writable
.writableLength
numberRequiredhighWaterMark
.writableNeedDrain
booleanRequiredtrue
if the stream's buffer has been full and stream will emit 'drain'
.writableObjectMode
booleanRequiredobjectMode
of a given Writable
stream.Symbol.for('nodejs.rejection')
See how to write a custom rejection handler
.captureRejections
booleanRequireddefaultMaxListeners
numberRequired10
listeners can be registered for any single event. This limit can be changed for individual EventEmitter
instances using the emitter.setMaxListeners(n)
method. To change the default for _all_EventEmitter
instances, the events.defaultMaxListeners
property can be used. If this value is not a positive number, a RangeError
is thrown. Take caution when setting the events.defaultMaxListeners
because the change affects _all_EventEmitter
instances, including those created before the change is made. However, calling emitter.setMaxListeners(n)
still has precedence over events.defaultMaxListeners
. This is not a hard limit. The EventEmitter
instance will allow more listeners to be added but will output a trace warning to stderr indicating that a "possible EventEmitter memory leak" has been detected. For any singleEventEmitter
, the emitter.getMaxListeners()
and emitter.setMaxListeners()
methods can be used to temporarily avoid this warning: js import { EventEmitter } from 'node:events'; const emitter = new EventEmitter(); emitter.setMaxListeners(emitter.getMaxListeners() + 1); emitter.once('event', () => { // do stuff emitter.setMaxListeners(Math.max(emitter.getMaxListeners() - 1, 0)); });
The --trace-warnings
command-line flag can be used to display the stack trace for such warnings. The emitted warning can be inspected with process.on('warning')
and will have the additional emitter
, type
, and count
properties, referring to the event emitter instance, the event's name and the number of attached listeners, respectively. Its name
property is set to 'MaxListenersExceededWarning'
.'error'
events. Listeners installed using this symbol are called before the regular'error'
listeners are called. Installing a listener using this symbol does not change the behavior once an'error'
event is emitted. Therefore, the process will still crash if no regular 'error'
listener is installed.Methods
[asyncDispose]
Calls readable.destroy()
with an AbortError
and returns a promise that fulfills when the stream is finished.
Returns
Promise
Promise<void>RequiredSince
v20.4.0
[asyncIterator]
Returns
[captureRejectionSymbol]
Parameters
Returns
void
void_construct
Parameters
Returns
void
void_destroy
Parameters
Returns
void
void_final
Parameters
Returns
void
void_flush
Parameters
Returns
void
void_read
Parameters
size
numberRequiredReturns
void
void_transform
Parameters
Returns
void
void_write
Parameters
Returns
void
void_writev
Parameters
chunks
{ chunk: any ; encoding: [BufferEncoding](/references/js-client/internal/types/internal.BufferEncoding) }[]RequiredReturns
void
voidaddListener
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Event emitter The defined events on documents including:
- close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
Parameters
event
"close"Requiredlistener
() => voidRequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"data"Requiredlistener
(chunk: any) => voidRequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"drain"Requiredlistener
() => voidRequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"end"Requiredlistener
() => voidRequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"error"RequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"finish"Requiredlistener
() => voidRequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"pause"Requiredlistener
() => voidRequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"pipe"RequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"readable"Requiredlistener
() => voidRequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"resume"Requiredlistener
() => voidRequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
"unpipe"RequiredReturns
**addListener**(event, listener): [PassThrough](/references/js-client/internal/classes/internal.PassThrough)
Parameters
event
string | symbolRequiredlistener
(...args: any[]) => voidRequiredReturns
asIndexedPairs
This method returns a new stream with chunks of the underlying stream paired with a counter
in the form [index, chunk]
. The first index value is 0
and it increases by 1 for each chunk produced.
Parameters
options
Pick<ArrayOptions, "signal">Returns
Since
v17.5.0
compose
Parameters
options
objectoptions.signal
AbortSignalRequiredReturns
T
TRequiredcork
The writable.cork()
method forces all written data to be buffered in memory.
The buffered data will be flushed when either the uncork or end methods are called.
The primary intent of writable.cork()
is to accommodate a situation in which
several small chunks are written to the stream in rapid succession. Instead of
immediately forwarding them to the underlying destination, writable.cork()
buffers all the chunks until writable.uncork()
is called, which will pass them
all to writable._writev()
, if present. This prevents a head-of-line blocking
situation where data is being buffered while waiting for the first small chunk
to be processed. However, use of writable.cork()
without implementingwritable._writev()
may have an adverse effect on throughput.
See also: writable.uncork()
, writable._writev()
.
Returns
void
voidSince
v0.11.2
destroy
Destroy the stream. Optionally emit an 'error'
event, and emit a 'close'
event (unless emitClose
is set to false
). After this call, the readable
stream will release any internal resources and subsequent calls to push()
will be ignored.
Once destroy()
has been called any further calls will be a no-op and no
further errors except from _destroy()
may be emitted as 'error'
.
Implementors should not override this method, but instead implement readable._destroy()
.
Parameters
error
Error'error'
eventReturns
Since
v8.0.0
drop
This method returns a new stream with the first limit chunks dropped from the start.
Parameters
limit
numberRequiredoptions
Pick<ArrayOptions, "signal">