Class PackrStream
                 
                    
                  Hierarchy
              
              - Transform- PackrStream
 
Index
Constructors
Methods
Properties
Constructors
constructor
- new PackrStream(
 options?:
 | Options
 | { allowHalfOpen: boolean; emitClose: boolean; highWaterMark: number },
 ): PackrStreamParameters- Optionaloptions: Options | { allowHalfOpen: boolean; emitClose: boolean; highWaterMark: number }
 Returns PackrStream
Methods
Optional_construct 
- Parameters- callback: (error?: Error) => void
 - Returns void
_destroy 
_final 
- Parameters- callback: (error?: Error) => void
 - Returns void
_flush 
- Parameters- callback: TransformCallback
 - Returns void
_read 
- Parameters- size: number
 - Returns void
_transform 
- Parameters- chunk: any
- encoding: BufferEncoding
- callback: TransformCallback
 - Returns void
_write 
- Parameters- chunk: any
- encoding: BufferEncoding
- callback: (error?: Error) => void
 - Returns void
Optional_writev 
[asyncDispose] 
- Returns Promise<void>
[asyncIterator] 
- Returns AsyncIterator<any>
Optional[captureRejectionSymbol]  
addListener 
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "close"
- listener: () => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "data"
- listener: (chunk: any) => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "drain"
- listener: () => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "end"
- listener: () => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "error"
- listener: (err: Error) => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "finish"
- listener: () => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "pause"
- listener: () => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "pipe"
- listener: (src: Readable) => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "readable"
- listener: () => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "resume"
- listener: () => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: "unpipe"
- listener: (src: Readable) => void
 - Returns this
- Event emitter The defined events on documents including: - close
- data
- drain
- end
- error
- finish
- pause
- pipe
- readable
- resume
- unpipe
 - Parameters- event: string | symbol
- listener: (...args: any[]) => void
 - Returns this
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- 0and it increases by 1 for each chunk produced.- Parameters- Optionaloptions: Pick<ArrayOptions, "signal">
 - Returns Readable- a stream of indexed pairs. 
compose
- compose<T extends ReadableStream>(
 stream:
 | T
 | ComposeFnParam
 | Iterable<T, any, any>
 | AsyncIterable<T, any, any>,
 options?: { signal: AbortSignal },
 ): TType Parameters- T extends ReadableStream
 Parameters- stream: T | ComposeFnParam | Iterable<T, any, any> | AsyncIterable<T, any, any>
- Optionaloptions: { signal: AbortSignal }
 Returns T
cork
- 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 implementing- writable._writev()may have an adverse effect on throughput.- See also: - writable.uncork(),- writable._writev().- Returns void
destroy
- Destroy the stream. Optionally emit an - 'error'event, and emit a- 'close'event (unless- emitCloseis 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- Optionalerror: Error- Error which will be passed as payload in - 'error'event
 - Returns this
drop
- This method returns a new stream with the first limit chunks dropped from the start. - Parameters- limit: numberthe number of chunks to drop from the readable. 
- Optionaloptions: Pick<ArrayOptions, "signal">
 - Returns Readable- a stream with limit chunks dropped from the start. 
- limit: number
emit
- Synchronously calls each of the listeners registered for the event named - eventName, in the order they were registered, passing the supplied arguments to each.- Returns - trueif the event had listeners,- falseotherwise.- import { EventEmitter } from 'node:events';
 const myEmitter = new EventEmitter();
 // First listener
 myEmitter.on('event', function firstListener() {
 console.log('Helloooo! first listener');
 });
 // Second listener
 myEmitter.on('event', function secondListener(arg1, arg2) {
 console.log(`event with parameters ${arg1}, ${arg2} in second listener`);
 });
 // Third listener
 myEmitter.on('event', function thirdListener(...args) {
 const parameters = args.join(', ');
 console.log(`event with parameters ${parameters} in third listener`);
 });
 console.log(myEmitter.listeners('event'));
 myEmitter.emit('event', 1, 2, 3, 4, 5);
 // Prints:
 // [
 // [Function: firstListener],
 // [Function: secondListener],
 // [Function: thirdListener]
 // ]
 // Helloooo! first listener
 // event with parameters 1, 2 in second listener
 // event with parameters 1, 2, 3, 4, 5 in third listener- Parameters- event: "close"
 - Returns boolean
- Parameters- event: "data"
- chunk: any
 - Returns boolean
- Parameters- event: "drain"
 - Returns boolean
- Parameters- event: "end"
 - Returns boolean
- Parameters- event: "error"
- err: Error
 - Returns boolean
- Parameters- event: "finish"
 - Returns boolean
- Parameters- event: "pause"
 - Returns boolean
- Parameters- event: "pipe"
- src: Readable
 - Returns boolean
- Parameters- event: "readable"
 - Returns boolean
- Parameters- event: "resume"
 - Returns boolean
- Parameters- event: "unpipe"
- src: Readable
 - Returns boolean
- Parameters- event: string | symbol
- ...args: any[]
 - Returns boolean
end
- Calling the - writable.end()method signals that no more data will be written to the- Writable. The optional- chunkand- encodingarguments allow one final additional chunk of data to be written immediately before closing the stream.- Calling the write method after calling end will raise an error. - // Write 'hello, ' and then end with 'world!'.
 import fs from 'node:fs';
 const file = fs.createWriteStream('example.txt');
 file.write('hello, ');
 file.end('world!');
 // Writing more now is not allowed!- Parameters- Optionalcb: () => void
 - Returns this
- Calling the - writable.end()method signals that no more data will be written to the- Writable. The optional- chunkand- encodingarguments allow one final additional chunk of data to be written immediately before closing the stream.- Calling the write method after calling end will raise an error. - // Write 'hello, ' and then end with 'world!'.
 import fs from 'node:fs';
 const file = fs.createWriteStream('example.txt');
 file.write('hello, ');
 file.end('world!');
 // Writing more now is not allowed!- Parameters- chunk: anyOptional data to write. For streams not operating in object mode, chunkmust be a {string}, {Buffer}, {TypedArray} or {DataView}. For object mode streams,chunkmay be any JavaScript value other thannull.
- Optionalcb: () => void
 - Returns this
- chunk: any
- Calling the - writable.end()method signals that no more data will be written to the- Writable. The optional- chunkand- encodingarguments allow one final additional chunk of data to be written immediately before closing the stream.- Calling the write method after calling end will raise an error. - // Write 'hello, ' and then end with 'world!'.
 import fs from 'node:fs';
 const file = fs.createWriteStream('example.txt');
 file.write('hello, ');
 file.end('world!');
 // Writing more now is not allowed!- Parameters- chunk: anyOptional data to write. For streams not operating in object mode, chunkmust be a {string}, {Buffer}, {TypedArray} or {DataView}. For object mode streams,chunkmay be any JavaScript value other thannull.
- encoding: BufferEncodingThe encoding if chunkis a string
- Optionalcb: () => void
 - Returns this
- chunk: any
eventNames 
- Returns an array listing the events for which the emitter has registered listeners. The values in the array are strings or - Symbols.- import { EventEmitter } from 'node:events';
 const myEE = new EventEmitter();
 myEE.on('foo', () => {});
 myEE.on('bar', () => {});
 const sym = Symbol('symbol');
 myEE.on(sym, () => {});
 console.log(myEE.eventNames());
 // Prints: [ 'foo', 'bar', Symbol(symbol) ]- Returns (string | symbol)[]
every
- every(
 fn: (
 data: any,
 options?: Pick<ArrayOptions, "signal">,
 ) => boolean | Promise<boolean>,
 options?: ArrayOptions,
 ): Promise<boolean>This method is similar to Array.prototype.everyand calls fn on each chunk in the stream to check if all awaited return values are truthy value for fn. Once an fn call on a chunkawaited return value is falsy, the stream is destroyed and the promise is fulfilled withfalse. If all of the fn calls on the chunks return a truthy value, the promise is fulfilled withtrue.ParametersReturns Promise<boolean>a promise evaluating to trueif fn returned a truthy value for every one of the chunks.
filter
- filter(
 fn: (
 data: any,
 options?: Pick<ArrayOptions, "signal">,
 ) => boolean | Promise<boolean>,
 options?: ArrayOptions,
 ): ReadableThis method allows filtering the stream. For each chunk in the stream the fn function will be called and if it returns a truthy value, the chunk will be passed to the result stream. If the fn function returns a promise - that promise will be awaited.ParametersReturns Readablea stream filtered with the predicate fn. 
find
- find<T>(
 fn: (data: any, options?: Pick<ArrayOptions, "signal">) => data is T,
 options?: ArrayOptions,
 ): Promise<T>This method is similar to Array.prototype.findand calls fn on each chunk in the stream to find a chunk with a truthy value for fn. Once an fn call's awaited return value is truthy, the stream is destroyed and the promise is fulfilled with value for which fn returned a truthy value. If all of the fn calls on the chunks return a falsy value, the promise is fulfilled withundefined.Type Parameters- T
 ParametersReturns Promise<T>a promise evaluating to the first chunk for which fn evaluated with a truthy value, or undefinedif no element was found.
- find(
 fn: (
 data: any,
 options?: Pick<ArrayOptions, "signal">,
 ) => boolean | Promise<boolean>,
 options?: ArrayOptions,
 ): Promise<any>This method is similar to Array.prototype.findand calls fn on each chunk in the stream to find a chunk with a truthy value for fn. Once an fn call's awaited return value is truthy, the stream is destroyed and the promise is fulfilled with value for which fn returned a truthy value. If all of the fn calls on the chunks return a falsy value, the promise is fulfilled withundefined.ParametersReturns Promise<any>a promise evaluating to the first chunk for which fn evaluated with a truthy value, or undefinedif no element was found.
flatMap 
- flatMap(
 fn: (data: any, options?: Pick<ArrayOptions, "signal">) => any,
 options?: ArrayOptions,
 ): ReadableThis method returns a new stream by applying the given callback to each chunk of the stream and then flattening the result. It is possible to return a stream or another iterable or async iterable from fn and the result streams will be merged (flattened) into the returned stream. Parameters- fn: (data: any, options?: Pick<ArrayOptions, "signal">) => anya function to map over every chunk in the stream. May be async. May be a stream or generator. 
- Optionaloptions: ArrayOptions
 Returns Readablea stream flat-mapped with the function fn. 
- fn: (data: any, options?: Pick<ArrayOptions, "signal">) => any
forEach 
- forEach(
 fn: (
 data: any,
 options?: Pick<ArrayOptions, "signal">,
 ) => void | Promise<void>,
 options?: ArrayOptions,
 ): Promise<void>This method allows iterating a stream. For each chunk in the stream the fn function will be called. If the fn function returns a promise - that promise will be awaited.This method is different from for await...ofloops in that it can optionally process chunks concurrently. In addition, aforEachiteration can only be stopped by having passed asignaloption and aborting the related AbortController whilefor await...ofcan be stopped withbreakorreturn. In either case the stream will be destroyed.This method is different from listening to the 'data'event in that it uses thereadableevent in the underlying machinary and can limit the number of concurrent fn calls.ParametersReturns Promise<void>a promise for when the stream has finished. 
getMaxListeners  
- Returns the current max listener value for the - EventEmitterwhich is either set by- emitter.setMaxListeners(n)or defaults to EventEmitter.defaultMaxListeners.- Returns number
isPaused 
- The - readable.isPaused()method returns the current operating state of the- Readable. This is used primarily by the mechanism that underlies the- readable.pipe()method. In most typical cases, there will be no reason to use this method directly.- const readable = new stream.Readable();
 readable.isPaused(); // === false
 readable.pause();
 readable.isPaused(); // === true
 readable.resume();
 readable.isPaused(); // === false- Returns boolean
iterator
- The iterator created by this method gives users the option to cancel the destruction of the stream if the - for await...ofloop is exited by- return,- break, or- throw, or if the iterator should destroy the stream if the stream emitted an error during iteration.- Parameters- Optionaloptions: { destroyOnReturn?: boolean }- OptionaldestroyOnReturn?: boolean- When set to - false, calling- returnon the async iterator, or exiting a- for await...ofiteration using a- break,- return, or- throwwill not destroy the stream. Default:- true.
 
 - Returns AsyncIterator<any>
listenerCount 
- Returns the number of listeners listening for the event named - eventName. If- listeneris provided, it will return how many times the listener is found in the list of the listeners of the event.- Type Parameters- K
 - Parameters- eventName: string | symbolThe name of the event being listened for 
- Optionallistener: Function- The event handler function 
 - Returns number
listeners
- Returns a copy of the array of listeners for the event named - eventName.- server.on('connection', (stream) => {
 console.log('someone connected!');
 });
 console.log(util.inspect(server.listeners('connection')));
 // Prints: [ [Function] ]- Type Parameters- K
 - Parameters- eventName: string | symbol
 - Returns Function[]
map
- map(
 fn: (data: any, options?: Pick<ArrayOptions, "signal">) => any,
 options?: ArrayOptions,
 ): ReadableThis method allows mapping over the stream. The fn function will be called for every chunk in the stream. If the fn function returns a promise - that promise will be awaited before being passed to the result stream.Parameters- fn: (data: any, options?: Pick<ArrayOptions, "signal">) => anya function to map over every chunk in the stream. Async or not. 
- Optionaloptions: ArrayOptions
 Returns Readablea stream mapped with the function fn. 
- fn: (data: any, options?: Pick<ArrayOptions, "signal">) => any
off
on
- Adds the - listenerfunction to the end of the listeners array for the event named- eventName. No checks are made to see if the- listenerhas already been added. Multiple calls passing the same combination of- eventNameand- listenerwill result in the- listenerbeing added, and called, multiple times.- server.on('connection', (stream) => {
 console.log('someone connected!');
 });- Returns a reference to the - EventEmitter, so that calls can be chained.- By default, event listeners are invoked in the order they are added. The - emitter.prependListener()method can be used as an alternative to add the event listener to the beginning of the listeners array.- import { EventEmitter } from 'node:events';
 const myEE = new EventEmitter();
 myEE.on('foo', () => console.log('a'));
 myEE.prependListener('foo', () => console.log('b'));
 myEE.emit('foo');
 // Prints:
 // b
 // a- Parameters- event: "close"
- listener: () => voidThe callback function 
 - Returns this
- Parameters- event: "data"
- listener: (chunk: any) => void
 - Returns this
- Parameters- event: "drain"
- listener: () => void
 - Returns this
- Parameters- event: "end"
- listener: () => void
 - Returns this
- Parameters- event: "error"
- listener: (err: Error) => void
 - Returns this
- Parameters- event: "finish"
- listener: () => void
 - Returns this
- Parameters- event: "pause"
- listener: () => void
 - Returns this
- Parameters- event: "pipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: "readable"
- listener: () => void
 - Returns this
- Parameters- event: "resume"
- listener: () => void
 - Returns this
- Parameters- event: "unpipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: string | symbol
- listener: (...args: any[]) => void
 - Returns this
once
- Adds a one-time - listenerfunction for the event named- eventName. The next time- eventNameis triggered, this listener is removed and then invoked.- server.once('connection', (stream) => {
 console.log('Ah, we have our first user!');
 });- Returns a reference to the - EventEmitter, so that calls can be chained.- By default, event listeners are invoked in the order they are added. The - emitter.prependOnceListener()method can be used as an alternative to add the event listener to the beginning of the listeners array.- import { EventEmitter } from 'node:events';
 const myEE = new EventEmitter();
 myEE.once('foo', () => console.log('a'));
 myEE.prependOnceListener('foo', () => console.log('b'));
 myEE.emit('foo');
 // Prints:
 // b
 // a- Parameters- event: "close"
- listener: () => voidThe callback function 
 - Returns this
- Parameters- event: "data"
- listener: (chunk: any) => void
 - Returns this
- Parameters- event: "drain"
- listener: () => void
 - Returns this
- Parameters- event: "end"
- listener: () => void
 - Returns this
- Parameters- event: "error"
- listener: (err: Error) => void
 - Returns this
- Parameters- event: "finish"
- listener: () => void
 - Returns this
- Parameters- event: "pause"
- listener: () => void
 - Returns this
- Parameters- event: "pipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: "readable"
- listener: () => void
 - Returns this
- Parameters- event: "resume"
- listener: () => void
 - Returns this
- Parameters- event: "unpipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: string | symbol
- listener: (...args: any[]) => void
 - Returns this
pause
- The - readable.pause()method will cause a stream in flowing mode to stop emitting- 'data'events, switching out of flowing mode. Any data that becomes available will remain in the internal buffer.- const readable = getReadableStreamSomehow();
 readable.on('data', (chunk) => {
 console.log(`Received ${chunk.length} bytes of data.`);
 readable.pause();
 console.log('There will be no additional data for 1 second.');
 setTimeout(() => {
 console.log('Now data will start flowing again.');
 readable.resume();
 }, 1000);
 });- The - readable.pause()method has no effect if there is a- 'readable'event listener.- Returns this
pipe
prependListener 
- Adds the - listenerfunction to the beginning of the listeners array for the event named- eventName. No checks are made to see if the- listenerhas already been added. Multiple calls passing the same combination of- eventNameand- listenerwill result in the- listenerbeing added, and called, multiple times.- server.prependListener('connection', (stream) => {
 console.log('someone connected!');
 });- Returns a reference to the - EventEmitter, so that calls can be chained.- Parameters- event: "close"
- listener: () => voidThe callback function 
 - Returns this
- Parameters- event: "data"
- listener: (chunk: any) => void
 - Returns this
- Parameters- event: "drain"
- listener: () => void
 - Returns this
- Parameters- event: "end"
- listener: () => void
 - Returns this
- Parameters- event: "error"
- listener: (err: Error) => void
 - Returns this
- Parameters- event: "finish"
- listener: () => void
 - Returns this
- Parameters- event: "pause"
- listener: () => void
 - Returns this
- Parameters- event: "pipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: "readable"
- listener: () => void
 - Returns this
- Parameters- event: "resume"
- listener: () => void
 - Returns this
- Parameters- event: "unpipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: string | symbol
- listener: (...args: any[]) => void
 - Returns this
prependOnceListener  
- Adds a one-time - listenerfunction for the event named- eventNameto the beginning of the listeners array. The next time- eventNameis triggered, this listener is removed, and then invoked.- server.prependOnceListener('connection', (stream) => {
 console.log('Ah, we have our first user!');
 });- Returns a reference to the - EventEmitter, so that calls can be chained.- Parameters- event: "close"
- listener: () => voidThe callback function 
 - Returns this
- Parameters- event: "data"
- listener: (chunk: any) => void
 - Returns this
- Parameters- event: "drain"
- listener: () => void
 - Returns this
- Parameters- event: "end"
- listener: () => void
 - Returns this
- Parameters- event: "error"
- listener: (err: Error) => void
 - Returns this
- Parameters- event: "finish"
- listener: () => void
 - Returns this
- Parameters- event: "pause"
- listener: () => void
 - Returns this
- Parameters- event: "pipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: "readable"
- listener: () => void
 - Returns this
- Parameters- event: "resume"
- listener: () => void
 - Returns this
- Parameters- event: "unpipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: string | symbol
- listener: (...args: any[]) => void
 - Returns this
push
- Parameters- chunk: any
- Optionalencoding: BufferEncoding
 - Returns boolean
rawListeners 
- Returns a copy of the array of listeners for the event named - eventName, including any wrappers (such as those created by- .once()).- import { EventEmitter } from 'node:events';
 const emitter = new EventEmitter();
 emitter.once('log', () => console.log('log once'));
 // Returns a new Array with a function `onceWrapper` which has a property
 // `listener` which contains the original listener bound above
 const listeners = emitter.rawListeners('log');
 const logFnWrapper = listeners[0];
 // Logs "log once" to the console and does not unbind the `once` event
 logFnWrapper.listener();
 // Logs "log once" to the console and removes the listener
 logFnWrapper();
 emitter.on('log', () => console.log('log persistently'));
 // Will return a new Array with a single function bound by `.on()` above
 const newListeners = emitter.rawListeners('log');
 // Logs "log persistently" twice
 newListeners[0]();
 emitter.emit('log');- Type Parameters- K
 - Parameters- eventName: string | symbol
 - Returns Function[]
read
- The - readable.read()method reads data out of the internal buffer and returns it. If no data is available to be read,- nullis returned. By default, the data is returned as a- Bufferobject unless an encoding has been specified using the- readable.setEncoding()method or the stream is operating in object mode.- The optional - sizeargument specifies a specific number of bytes to read. If- sizebytes are not available to be read,- nullwill be returned unless the stream has ended, in which case all of the data remaining in the internal buffer will be returned.- If the - sizeargument is not specified, all of the data contained in the internal buffer will be returned.- The - sizeargument must be less than or equal to 1 GiB.- The - readable.read()method should only be called on- Readablestreams operating in paused mode. In flowing mode,- readable.read()is called automatically until the internal buffer is fully drained.- const readable = getReadableStreamSomehow();
 // 'readable' may be triggered multiple times as data is buffered in
 readable.on('readable', () => {
 let chunk;
 console.log('Stream is readable (new data received in buffer)');
 // Use a loop to make sure we read all currently available data
 while (null !== (chunk = readable.read())) {
 console.log(`Read ${chunk.length} bytes of data...`);
 }
 });
 // 'end' will be triggered once when there is no more data available
 readable.on('end', () => {
 console.log('Reached end of stream.');
 });- Each call to - readable.read()returns a chunk of data, or- null. The chunks are not concatenated. A- whileloop is necessary to consume all data currently in the buffer. When reading a large file- .read()may return- null, having consumed all buffered content so far, but there is still more data to come not yet buffered. In this case a new- 'readable'event will be emitted when there is more data in the buffer. Finally the- 'end'event will be emitted when there is no more data to come.- Therefore to read a file's whole contents from a - readable, it is necessary to collect chunks across multiple- 'readable'events:- const chunks = [];
 readable.on('readable', () => {
 let chunk;
 while (null !== (chunk = readable.read())) {
 chunks.push(chunk);
 }
 });
 readable.on('end', () => {
 const content = chunks.join('');
 });- A - Readablestream in object mode will always return a single item from a call to- readable.read(size), regardless of the value of the- sizeargument.- If the - readable.read()method returns a chunk of data, a- 'data'event will also be emitted.- Calling read after the - 'end'event has been emitted will return- null. No runtime error will be raised.- Parameters- Optionalsize: number- Optional argument to specify how much data to read. 
 - Returns any
reduce
- reduce<T = any>(
 fn: (
 previous: any,
 data: any,
 options?: Pick<ArrayOptions, "signal">,
 ) => T,
 initial?: undefined,
 options?: Pick<ArrayOptions, "signal">,
 ): Promise<T>This method calls fn on each chunk of the stream in order, passing it the result from the calculation on the previous element. It returns a promise for the final value of the reduction. If no initial value is supplied the first chunk of the stream is used as the initial value. If the stream is empty, the promise is rejected with a TypeErrorwith theERR_INVALID_ARGScode property.The reducer function iterates the stream element-by-element which means that there is no concurrency parameter or parallelism. To perform a reduce concurrently, you can extract the async function to readable.mapmethod.Type Parameters- T = any
 ParametersReturns Promise<T>a promise for the final value of the reduction. 
- reduce<T = any>(
 fn: (
 previous: T,
 data: any,
 options?: Pick<ArrayOptions, "signal">,
 ) => T,
 initial: T,
 options?: Pick<ArrayOptions, "signal">,
 ): Promise<T>This method calls fn on each chunk of the stream in order, passing it the result from the calculation on the previous element. It returns a promise for the final value of the reduction. If no initial value is supplied the first chunk of the stream is used as the initial value. If the stream is empty, the promise is rejected with a TypeErrorwith theERR_INVALID_ARGScode property.The reducer function iterates the stream element-by-element which means that there is no concurrency parameter or parallelism. To perform a reduce concurrently, you can extract the async function to readable.mapmethod.Type Parameters- T = any
 ParametersReturns Promise<T>a promise for the final value of the reduction. 
removeAllListeners  
- Removes all listeners, or those of the specified - eventName.- It is bad practice to remove listeners added elsewhere in the code, particularly when the - EventEmitterinstance was created by some other component or module (e.g. sockets or file streams).- Returns a reference to the - EventEmitter, so that calls can be chained.- Parameters- OptionaleventName: string | symbol
 - Returns this
removeListener 
- Removes the specified - listenerfrom the listener array for the event named- eventName.- const callback = (stream) => {
 console.log('someone connected!');
 };
 server.on('connection', callback);
 // ...
 server.removeListener('connection', callback);- removeListener()will remove, at most, one instance of a listener from the listener array. If any single listener has been added multiple times to the listener array for the specified- eventName, then- removeListener()must be called multiple times to remove each instance.- Once an event is emitted, all listeners attached to it at the time of emitting are called in order. This implies that any - removeListener()or- removeAllListeners()calls after emitting and before the last listener finishes execution will not remove them from- emit()in progress. Subsequent events behave as expected.- import { EventEmitter } from 'node:events';
 class MyEmitter extends EventEmitter {}
 const myEmitter = new MyEmitter();
 const callbackA = () => {
 console.log('A');
 myEmitter.removeListener('event', callbackB);
 };
 const callbackB = () => {
 console.log('B');
 };
 myEmitter.on('event', callbackA);
 myEmitter.on('event', callbackB);
 // callbackA removes listener callbackB but it will still be called.
 // Internal listener array at time of emit [callbackA, callbackB]
 myEmitter.emit('event');
 // Prints:
 // A
 // B
 // callbackB is now removed.
 // Internal listener array [callbackA]
 myEmitter.emit('event');
 // Prints:
 // A- Because listeners are managed using an internal array, calling this will change the position indices of any listener registered after the listener being removed. This will not impact the order in which listeners are called, but it means that any copies of the listener array as returned by the - emitter.listeners()method will need to be recreated.- When a single function has been added as a handler multiple times for a single event (as in the example below), - removeListener()will remove the most recently added instance. In the example the- once('ping')listener is removed:- import { EventEmitter } from 'node:events';
 const ee = new EventEmitter();
 function pong() {
 console.log('pong');
 }
 ee.on('ping', pong);
 ee.once('ping', pong);
 ee.removeListener('ping', pong);
 ee.emit('ping');
 ee.emit('ping');- Returns a reference to the - EventEmitter, so that calls can be chained.- Parameters- event: "close"
- listener: () => void
 - Returns this
- Parameters- event: "data"
- listener: (chunk: any) => void
 - Returns this
- Parameters- event: "drain"
- listener: () => void
 - Returns this
- Parameters- event: "end"
- listener: () => void
 - Returns this
- Parameters- event: "error"
- listener: (err: Error) => void
 - Returns this
- Parameters- event: "finish"
- listener: () => void
 - Returns this
- Parameters- event: "pause"
- listener: () => void
 - Returns this
- Parameters- event: "pipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: "readable"
- listener: () => void
 - Returns this
- Parameters- event: "resume"
- listener: () => void
 - Returns this
- Parameters- event: "unpipe"
- listener: (src: Readable) => void
 - Returns this
- Parameters- event: string | symbol
- listener: (...args: any[]) => void
 - Returns this
resume
- The - readable.resume()method causes an explicitly paused- Readablestream to resume emitting- 'data'events, switching the stream into flowing mode.- The - readable.resume()method can be used to fully consume the data from a stream without actually processing any of that data:- getReadableStreamSomehow()
 .resume()
 .on('end', () => {
 console.log('Reached the end, but did not read anything.');
 });- The - readable.resume()method has no effect if there is a- 'readable'event listener.- Returns this
setDefaultEncoding  
setEncoding 
- The - readable.setEncoding()method sets the character encoding for data read from the- Readablestream.- By default, no encoding is assigned and stream data will be returned as - Bufferobjects. Setting an encoding causes the stream data to be returned as strings of the specified encoding rather than as- Bufferobjects. For instance, calling- readable.setEncoding('utf8')will cause the output data to be interpreted as UTF-8 data, and passed as strings. Calling- readable.setEncoding('hex')will cause the data to be encoded in hexadecimal string format.- The - Readablestream will properly handle multi-byte characters delivered through the stream that would otherwise become improperly decoded if simply pulled from the stream as- Bufferobjects.- const readable = getReadableStreamSomehow();
 readable.setEncoding('utf8');
 readable.on('data', (chunk) => {
 assert.equal(typeof chunk, 'string');
 console.log('Got %d characters of string data:', chunk.length);
 });- Parameters- encoding: BufferEncodingThe encoding to use. 
 - Returns this
- encoding: BufferEncoding
setMaxListeners  
- By default - EventEmitters will print a warning if more than- 10listeners are added for a particular event. This is a useful default that helps finding memory leaks. The- emitter.setMaxListeners()method allows the limit to be modified for this specific- EventEmitterinstance. The value can be set to- Infinity(or- 0) to indicate an unlimited number of listeners.- Returns a reference to the - EventEmitter, so that calls can be chained.- Parameters- n: number
 - Returns this
some
- some(
 fn: (
 data: any,
 options?: Pick<ArrayOptions, "signal">,
 ) => boolean | Promise<boolean>,
 options?: ArrayOptions,
 ): Promise<boolean>This method is similar to Array.prototype.someand calls fn on each chunk in the stream until the awaited return value istrue(or any truthy value). Once an fn call on a chunkawaited return value is truthy, the stream is destroyed and the promise is fulfilled withtrue. If none of the fn calls on the chunks return a truthy value, the promise is fulfilled withfalse.ParametersReturns Promise<boolean>a promise evaluating to trueif fn returned a truthy value for at least one of the chunks.
take
- This method returns a new stream with the first limit chunks. - Parameters- limit: numberthe number of chunks to take from the readable. 
- Optionaloptions: Pick<ArrayOptions, "signal">
 - Returns Readable- a stream with limit chunks taken. 
- limit: number
toArray 
- This method allows easily obtaining the contents of a stream. - As this method reads the entire stream into memory, it negates the benefits of streams. It's intended for interoperability and convenience, not as the primary way to consume streams. - Parameters- Optionaloptions: Pick<ArrayOptions, "signal">
 - Returns Promise<any[]>- a promise containing an array with the contents of the stream. 
uncork
- The - writable.uncork()method flushes all data buffered since cork was called.- When using - writable.cork()and- writable.uncork()to manage the buffering of writes to a stream, defer calls to- writable.uncork()using- process.nextTick(). Doing so allows batching of all- writable.write()calls that occur within a given Node.js event loop phase.- stream.cork();
 stream.write('some ');
 stream.write('data ');
 process.nextTick(() => stream.uncork());- If the - writable.cork()method is called multiple times on a stream, the same number of calls to- writable.uncork()must be called to flush the buffered data.- stream.cork();
 stream.write('some ');
 stream.cork();
 stream.write('data ');
 process.nextTick(() => {
 stream.uncork();
 // The data will not be flushed until uncork() is called a second time.
 stream.uncork();
 });- See also: - writable.cork().- Returns void
unpipe
- The - readable.unpipe()method detaches a- Writablestream previously attached using the pipe method.- If the - destinationis not specified, then all pipes are detached.- If the - destinationis specified, but no pipe is set up for it, then the method does nothing.- import fs from 'node:fs';
 const readable = getReadableStreamSomehow();
 const writable = fs.createWriteStream('file.txt');
 // All the data from readable goes into 'file.txt',
 // but only for the first second.
 readable.pipe(writable);
 setTimeout(() => {
 console.log('Stop writing to file.txt.');
 readable.unpipe(writable);
 console.log('Manually close the file stream.');
 writable.end();
 }, 1000);- Parameters- Optionaldestination: WritableStream- Optional specific stream to unpipe 
 - Returns this
unshift
- Passing - chunkas- nullsignals the end of the stream (EOF) and behaves the same as- readable.push(null), after which no more data can be written. The EOF signal is put at the end of the buffer and any buffered data will still be flushed.- The - readable.unshift()method pushes a chunk of data back into the internal buffer. This is useful in certain situations where a stream is being consumed by code that needs to "un-consume" some amount of data that it has optimistically pulled out of the source, so that the data can be passed on to some other party.- The - stream.unshift(chunk)method cannot be called after the- 'end'event has been emitted or a runtime error will be thrown.- Developers using - stream.unshift()often should consider switching to use of a- Transformstream instead. See the- API for stream implementerssection for more information.- // Pull off a header delimited by \n\n.
 // Use unshift() if we get too much.
 // Call the callback with (error, header, stream).
 import { StringDecoder } from 'node:string_decoder';
 function parseHeader(stream, callback) {
 stream.on('error', callback);
 stream.on('readable', onReadable);
 const decoder = new StringDecoder('utf8');
 let header = '';
 function onReadable() {
 let chunk;
 while (null !== (chunk = stream.read())) {
 const str = decoder.write(chunk);
 if (str.includes('\n\n')) {
 // Found the header boundary.
 const split = str.split(/\n\n/);
 header += split.shift();
 const remaining = split.join('\n\n');
 const buf = Buffer.from(remaining, 'utf8');
 stream.removeListener('error', callback);
 // Remove the 'readable' listener before unshifting.
 stream.removeListener('readable', onReadable);
 if (buf.length)
 stream.unshift(buf);
 // Now the body of the message can be read from the stream.
 callback(null, header, stream);
 return;
 }
 // Still reading the header.
 header += str;
 }
 }
 }- Unlike push, - stream.unshift(chunk)will not end the reading process by resetting the internal reading state of the stream. This can cause unexpected results if- readable.unshift()is called during a read (i.e. from within a _read implementation on a custom stream). Following the call to- readable.unshift()with an immediate push will reset the reading state appropriately, however it is best to simply avoid calling- readable.unshift()while in the process of performing a read.- Parameters- chunk: anyChunk of data to unshift onto the read queue. For streams not operating in object mode, chunkmust be a {string}, {Buffer}, {TypedArray}, {DataView} ornull. For object mode streams,chunkmay be any JavaScript value.
- Optionalencoding: BufferEncoding- Encoding of string chunks. Must be a valid - Bufferencoding, such as- 'utf8'or- 'ascii'.
 - Returns void
- chunk: any
wrap
- Prior to Node.js 0.10, streams did not implement the entire - node:streammodule API as it is currently defined. (See- Compatibilityfor more information.)- When using an older Node.js library that emits - 'data'events and has a pause method that is advisory only, the- readable.wrap()method can be used to create a- Readablestream that uses the old stream as its data source.- It will rarely be necessary to use - readable.wrap()but the method has been provided as a convenience for interacting with older Node.js applications and libraries.- import { OldReader } from './old-api-module.js';
 import { Readable } from 'node:stream';
 const oreader = new OldReader();
 const myReader = new Readable().wrap(oreader);
 myReader.on('readable', () => {
 myReader.read(); // etc.
 });- Parameters- stream: ReadableStreamAn "old style" readable stream 
 - Returns this
- stream: ReadableStream
write
- The - writable.write()method writes some data to the stream, and calls the supplied- callbackonce the data has been fully handled. If an error occurs, the- callbackwill be called with the error as its first argument. The- callbackis called asynchronously and before- 'error'is emitted.- The return value is - trueif the internal buffer is less than the- highWaterMarkconfigured when the stream was created after admitting- chunk. If- falseis returned, further attempts to write data to the stream should stop until the- 'drain'event is emitted.- While a stream is not draining, calls to - write()will buffer- chunk, and return false. Once all currently buffered chunks are drained (accepted for delivery by the operating system), the- 'drain'event will be emitted. Once- write()returns false, do not write more chunks until the- 'drain'event is emitted. While calling- write()on a stream that is not draining is allowed, Node.js will buffer all written chunks until maximum memory usage occurs, at which point it will abort unconditionally. Even before it aborts, high memory usage will cause poor garbage collector performance and high RSS (which is not typically released back to the system, even after the memory is no longer required). Since TCP sockets may never drain if the remote peer does not read the data, writing a socket that is not draining may lead to a remotely exploitable vulnerability.- Writing data while the stream is not draining is particularly problematic for a - Transform, because the- Transformstreams are paused by default until they are piped or a- 'data'or- 'readable'event handler is added.- If the data to be written can be generated or fetched on demand, it is recommended to encapsulate the logic into a - Readableand use pipe. However, if calling- write()is preferred, it is possible to respect backpressure and avoid memory issues using the- 'drain'event:- function write(data, cb) {
 if (!stream.write(data)) {
 stream.once('drain', cb);
 } else {
 process.nextTick(cb);
 }
 }
 // Wait for cb to be called before doing any other write.
 write('hello', () => {
 console.log('Write completed, do more writes now.');
 });- A - Writablestream in object mode will always ignore the- encodingargument.- Parameters- chunk: anyOptional data to write. For streams not operating in object mode, chunkmust be a {string}, {Buffer}, {TypedArray} or {DataView}. For object mode streams,chunkmay be any JavaScript value other thannull.
- Optionalcallback: (error: Error) => void- Callback for when this chunk of data is flushed. 
 - Returns boolean- falseif the stream wishes for the calling code to wait for the- 'drain'event to be emitted before continuing to write additional data; otherwise- true.
- chunk: any
- The - writable.write()method writes some data to the stream, and calls the supplied- callbackonce the data has been fully handled. If an error occurs, the- callbackwill be called with the error as its first argument. The- callbackis called asynchronously and before- 'error'is emitted.- The return value is - trueif the internal buffer is less than the- highWaterMarkconfigured when the stream was created after admitting- chunk. If- falseis returned, further attempts to write data to the stream should stop until the- 'drain'event is emitted.- While a stream is not draining, calls to - write()will buffer- chunk, and return false. Once all currently buffered chunks are drained (accepted for delivery by the operating system), the- 'drain'event will be emitted. Once- write()returns false, do not write more chunks until the- 'drain'event is emitted. While calling- write()on a stream that is not draining is allowed, Node.js will buffer all written chunks until maximum memory usage occurs, at which point it will abort unconditionally. Even before it aborts, high memory usage will cause poor garbage collector performance and high RSS (which is not typically released back to the system, even after the memory is no longer required). Since TCP sockets may never drain if the remote peer does not read the data, writing a socket that is not draining may lead to a remotely exploitable vulnerability.- Writing data while the stream is not draining is particularly problematic for a - Transform, because the- Transformstreams are paused by default until they are piped or a- 'data'or- 'readable'event handler is added.- If the data to be written can be generated or fetched on demand, it is recommended to encapsulate the logic into a - Readableand use pipe. However, if calling- write()is preferred, it is possible to respect backpressure and avoid memory issues using the- 'drain'event:- function write(data, cb) {
 if (!stream.write(data)) {
 stream.once('drain', cb);
 } else {
 process.nextTick(cb);
 }
 }
 // Wait for cb to be called before doing any other write.
 write('hello', () => {
 console.log('Write completed, do more writes now.');
 });- A - Writablestream in object mode will always ignore the- encodingargument.- Parameters- chunk: anyOptional data to write. For streams not operating in object mode, chunkmust be a {string}, {Buffer}, {TypedArray} or {DataView}. For object mode streams,chunkmay be any JavaScript value other thannull.
- encoding: BufferEncodingThe encoding, if chunkis a string.
- Optionalcallback: (error: Error) => void- Callback for when this chunk of data is flushed. 
 - Returns boolean- falseif the stream wishes for the calling code to wait for the- 'drain'event to be emitted before continuing to write additional data; otherwise- true.
- chunk: any
StaticaddAbortListener  
- Listens once to the - abortevent on the provided- signal.- Listening to the - abortevent on abort signals is unsafe and may lead to resource leaks since another third party with the signal can call- e.stopImmediatePropagation(). Unfortunately Node.js cannot change this since it would violate the web standard. Additionally, the original API makes it easy to forget to remove listeners.- This API allows safely using - AbortSignals in Node.js APIs by solving these two issues by listening to the event such that- stopImmediatePropagationdoes not prevent the listener from running.- Returns a disposable so that it may be unsubscribed from more easily. - import { addAbortListener } from 'node:events';
 function example(signal) {
 let disposable;
 try {
 signal.addEventListener('abort', (e) => e.stopImmediatePropagation());
 disposable = addAbortListener(signal, (e) => {
 // Do something when signal is aborted.
 });
 } finally {
 disposable?.[Symbol.dispose]();
 }
 }- Parameters- signal: AbortSignal
- resource: (event: Event) => void
 - Returns Disposable- Disposable that removes the - abortlistener.
Staticfrom
- from(
 src:
 | string
 | Object
 | Promise<any>
 | ArrayBuffer
 | Stream
 | Blob
 | Iterable<any, any, any>
 | AsyncIterable<any, any, any>
 | AsyncGeneratorFunction,
 ): DuplexA utility method for creating duplex streams. - Streamconverts writable stream into writable- Duplexand readable stream to- Duplex.
- Blobconverts into readable- Duplex.
- stringconverts into readable- Duplex.
- ArrayBufferconverts into readable- Duplex.
- AsyncIterableconverts into a readable- Duplex. Cannot yield- null.
- AsyncGeneratorFunctionconverts into a readable/writable transform- Duplex. Must take a source- AsyncIterableas first parameter. Cannot yield- null.
- AsyncFunctionconverts into a writable- Duplex. Must return either- nullor- undefined
- Object ({ writable, readable })converts- readableand- writableinto- Streamand then combines them into- Duplexwhere the- Duplexwill write to the- writableand read from the- readable.
- Promiseconverts into readable- Duplex. Value- nullis ignored.
 Parameters- src: 
 | string
 | Object
 | Promise<any>
 | ArrayBuffer
 | Stream
 | Blob
 | Iterable<any, any, any>
 | AsyncIterable<any, any, any>
 | AsyncGeneratorFunction
 Returns Duplex
StaticfromWeb 
- fromWeb(
 duplexStream: { readable: ReadableStream; writable: WritableStream },
 options?: Pick<
 DuplexOptions,
 | "allowHalfOpen"
 | "decodeStrings"
 | "encoding"
 | "highWaterMark"
 | "objectMode"
 | "signal",
 >,
 ): DuplexA utility method for creating a Duplexfrom a webReadableStreamandWritableStream.Parameters- duplexStream: { readable: ReadableStream; writable: WritableStream }
- Optionaloptions: Pick<
 DuplexOptions,
 | "allowHalfOpen"
 | "decodeStrings"
 | "encoding"
 | "highWaterMark"
 | "objectMode"
 | "signal",
 >
 Returns Duplex
StaticgetEventListeners  
- getEventListeners(
 emitter: EventTarget | EventEmitter<DefaultEventMap>,
 name: string | symbol,
 ): Function[]Returns a copy of the array of listeners for the event named eventName.For EventEmitters this behaves exactly the same as calling.listenerson the emitter.For EventTargets this is the only way to get the event listeners for the event target. This is useful for debugging and diagnostic purposes.import { getEventListeners, EventEmitter } from 'node:events';
 {
 const ee = new EventEmitter();
 const listener = () => console.log('Events are fun');
 ee.on('foo', listener);
 console.log(getEventListeners(ee, 'foo')); // [ [Function: listener] ]
 }
 {
 const et = new EventTarget();
 const listener = () => console.log('Events are fun');
 et.addEventListener('foo', listener);
 console.log(getEventListeners(et, 'foo')); // [ [Function: listener] ]
 }Parameters- emitter: EventTarget | EventEmitter<DefaultEventMap>
- name: string | symbol
 Returns Function[]
StaticgetMaxListeners  
- Returns the currently set max amount of listeners. - For - EventEmitters this behaves exactly the same as calling- .getMaxListenerson the emitter.- For - EventTargets this is the only way to get the max event listeners for the event target. If the number of event handlers on a single EventTarget exceeds the max set, the EventTarget will print a warning.- import { getMaxListeners, setMaxListeners, EventEmitter } from 'node:events';
 {
 const ee = new EventEmitter();
 console.log(getMaxListeners(ee)); // 10
 setMaxListeners(11, ee);
 console.log(getMaxListeners(ee)); // 11
 }
 {
 const et = new EventTarget();
 console.log(getMaxListeners(et)); // 10
 setMaxListeners(11, et);
 console.log(getMaxListeners(et)); // 11
 }- Parameters- emitter: EventTarget | EventEmitter<DefaultEventMap>
 - Returns number
StaticlistenerCount 
- A class method that returns the number of listeners for the given - eventNameregistered on the given- emitter.- import { EventEmitter, listenerCount } from 'node:events';
 const myEmitter = new EventEmitter();
 myEmitter.on('event', () => {});
 myEmitter.on('event', () => {});
 console.log(listenerCount(myEmitter, 'event'));
 // Prints: 2- Parameters- emitter: EventEmitterThe emitter to query 
- eventName: string | symbolThe event name 
 - Returns number
- emitter: EventEmitter
Staticon
- on(
 emitter: EventEmitter,
 eventName: string | symbol,
 options?: StaticEventEmitterIteratorOptions,
 ): AsyncIterator<any[]>import { on, EventEmitter } from 'node:events';
 import process from 'node:process';
 const ee = new EventEmitter();
 // Emit later on
 process.nextTick(() => {
 ee.emit('foo', 'bar');
 ee.emit('foo', 42);
 });
 for await (const event of on(ee, 'foo')) {
 // The execution of this inner block is synchronous and it
 // processes one event at a time (even with await). Do not use
 // if concurrent execution is required.
 console.log(event); // prints ['bar'] [42]
 }
 // Unreachable hereReturns an AsyncIteratorthat iterateseventNameevents. It will throw if theEventEmitteremits'error'. It removes all listeners when exiting the loop. Thevaluereturned by each iteration is an array composed of the emitted event arguments.An AbortSignalcan be used to cancel waiting on events:import { on, EventEmitter } from 'node:events';
 import process from 'node:process';
 const ac = new AbortController();
 (async () => {
 const ee = new EventEmitter();
 // Emit later on
 process.nextTick(() => {
 ee.emit('foo', 'bar');
 ee.emit('foo', 42);
 });
 for await (const event of on(ee, 'foo', { signal: ac.signal })) {
 // The execution of this inner block is synchronous and it
 // processes one event at a time (even with await). Do not use
 // if concurrent execution is required.
 console.log(event); // prints ['bar'] [42]
 }
 // Unreachable here
 })();
 process.nextTick(() => ac.abort());Use the closeoption to specify an array of event names that will end the iteration:import { on, EventEmitter } from 'node:events';
 import process from 'node:process';
 const ee = new EventEmitter();
 // Emit later on
 process.nextTick(() => {
 ee.emit('foo', 'bar');
 ee.emit('foo', 42);
 ee.emit('close');
 });
 for await (const event of on(ee, 'foo', { close: ['close'] })) {
 console.log(event); // prints ['bar'] [42]
 }
 // the loop will exit after 'close' is emitted
 console.log('done'); // prints 'done'Parameters- emitter: EventEmitter
- eventName: string | symbol
- Optionaloptions: StaticEventEmitterIteratorOptions
 Returns AsyncIterator<any[]>An AsyncIteratorthat iterateseventNameevents emitted by theemitter
- on(
 emitter: EventTarget,
 eventName: string,
 options?: StaticEventEmitterIteratorOptions,
 ): AsyncIterator<any[]>import { on, EventEmitter } from 'node:events';
 import process from 'node:process';
 const ee = new EventEmitter();
 // Emit later on
 process.nextTick(() => {
 ee.emit('foo', 'bar');
 ee.emit('foo', 42);
 });
 for await (const event of on(ee, 'foo')) {
 // The execution of this inner block is synchronous and it
 // processes one event at a time (even with await). Do not use
 // if concurrent execution is required.
 console.log(event); // prints ['bar'] [42]
 }
 // Unreachable hereReturns an AsyncIteratorthat iterateseventNameevents. It will throw if theEventEmitteremits'error'. It removes all listeners when exiting the loop. Thevaluereturned by each iteration is an array composed of the emitted event arguments.An AbortSignalcan be used to cancel waiting on events:import { on, EventEmitter } from 'node:events';
 import process from 'node:process';
 const ac = new AbortController();
 (async () => {
 const ee = new EventEmitter();
 // Emit later on
 process.nextTick(() => {
 ee.emit('foo', 'bar');
 ee.emit('foo', 42);
 });
 for await (const event of on(ee, 'foo', { signal: ac.signal })) {
 // The execution of this inner block is synchronous and it
 // processes one event at a time (even with await). Do not use
 // if concurrent execution is required.
 console.log(event); // prints ['bar'] [42]
 }
 // Unreachable here
 })();
 process.nextTick(() => ac.abort());Use the closeoption to specify an array of event names that will end the iteration:import { on, EventEmitter } from 'node:events';
 import process from 'node:process';
 const ee = new EventEmitter();
 // Emit later on
 process.nextTick(() => {
 ee.emit('foo', 'bar');
 ee.emit('foo', 42);
 ee.emit('close');
 });
 for await (const event of on(ee, 'foo', { close: ['close'] })) {
 console.log(event); // prints ['bar'] [42]
 }
 // the loop will exit after 'close' is emitted
 console.log('done'); // prints 'done'Parameters- emitter: EventTarget
- eventName: string
- Optionaloptions: StaticEventEmitterIteratorOptions
 Returns AsyncIterator<any[]>An AsyncIteratorthat iterateseventNameevents emitted by theemitter
Staticonce
- once(
 emitter: EventEmitter,
 eventName: string | symbol,
 options?: StaticEventEmitterOptions,
 ): Promise<any[]>Creates a Promisethat is fulfilled when theEventEmitteremits the given event or that is rejected if theEventEmitteremits'error'while waiting. ThePromisewill resolve with an array of all the arguments emitted to the given event.This method is intentionally generic and works with the web platform EventTarget interface, which has no special 'error'event semantics and does not listen to the'error'event.import { once, EventEmitter } from 'node:events';
 import process from 'node:process';
 const ee = new EventEmitter();
 process.nextTick(() => {
 ee.emit('myevent', 42);
 });
 const [value] = await once(ee, 'myevent');
 console.log(value);
 const err = new Error('kaboom');
 process.nextTick(() => {
 ee.emit('error', err);
 });
 try {
 await once(ee, 'myevent');
 } catch (err) {
 console.error('error happened', err);
 }The special handling of the 'error'event is only used whenevents.once()is used to wait for another event. Ifevents.once()is used to wait for the 'error'event itself, then it is treated as any other kind of event without special handling:import { EventEmitter, once } from 'node:events';
 const ee = new EventEmitter();
 once(ee, 'error')
 .then(([err]) => console.log('ok', err.message))
 .catch((err) => console.error('error', err.message));
 ee.emit('error', new Error('boom'));
 // Prints: ok boomAn AbortSignalcan be used to cancel waiting for the event:import { EventEmitter, once } from 'node:events';
 const ee = new EventEmitter();
 const ac = new AbortController();
 async function foo(emitter, event, signal) {
 try {
 await once(emitter, event, { signal });
 console.log('event emitted!');
 } catch (error) {
 if (error.name === 'AbortError') {
 console.error('Waiting for the event was canceled!');
 } else {
 console.error('There was an error', error.message);
 }
 }
 }
 foo(ee, 'foo', ac.signal);
 ac.abort(); // Abort waiting for the event
 ee.emit('foo'); // Prints: Waiting for the event was canceled!Parameters- emitter: EventEmitter
- eventName: string | symbol
- Optionaloptions: StaticEventEmitterOptions
 Returns Promise<any[]>
- once(
 emitter: EventTarget,
 eventName: string,
 options?: StaticEventEmitterOptions,
 ): Promise<any[]>Creates a Promisethat is fulfilled when theEventEmitteremits the given event or that is rejected if theEventEmitteremits'error'while waiting. ThePromisewill resolve with an array of all the arguments emitted to the given event.This method is intentionally generic and works with the web platform EventTarget interface, which has no special 'error'event semantics and does not listen to the'error'event.import { once, EventEmitter } from 'node:events';
 import process from 'node:process';
 const ee = new EventEmitter();
 process.nextTick(() => {
 ee.emit('myevent', 42);
 });
 const [value] = await once(ee, 'myevent');
 console.log(value);
 const err = new Error('kaboom');
 process.nextTick(() => {
 ee.emit('error', err);
 });
 try {
 await once(ee, 'myevent');
 } catch (err) {
 console.error('error happened', err);
 }The special handling of the 'error'event is only used whenevents.once()is used to wait for another event. Ifevents.once()is used to wait for the 'error'event itself, then it is treated as any other kind of event without special handling:import { EventEmitter, once } from 'node:events';
 const ee = new EventEmitter();
 once(ee, 'error')
 .then(([err]) => console.log('ok', err.message))
 .catch((err) => console.error('error', err.message));
 ee.emit('error', new Error('boom'));
 // Prints: ok boomAn AbortSignalcan be used to cancel waiting for the event:import { EventEmitter, once } from 'node:events';
 const ee = new EventEmitter();
 const ac = new AbortController();
 async function foo(emitter, event, signal) {
 try {
 await once(emitter, event, { signal });
 console.log('event emitted!');
 } catch (error) {
 if (error.name === 'AbortError') {
 console.error('Waiting for the event was canceled!');
 } else {
 console.error('There was an error', error.message);
 }
 }
 }
 foo(ee, 'foo', ac.signal);
 ac.abort(); // Abort waiting for the event
 ee.emit('foo'); // Prints: Waiting for the event was canceled!Parameters- emitter: EventTarget
- eventName: string
- Optionaloptions: StaticEventEmitterOptions
 Returns Promise<any[]>
StaticsetMaxListeners  
- setMaxListeners(
 n?: number,
 ...eventTargets: (EventTarget | EventEmitter<DefaultEventMap>)[],
 ): voidimport { setMaxListeners, EventEmitter } from 'node:events';
 const target = new EventTarget();
 const emitter = new EventEmitter();
 setMaxListeners(5, target, emitter);Parameters- Optionaln: number- A non-negative number. The maximum number of listeners per - EventTargetevent.
- ...eventTargets: (EventTarget | EventEmitter<DefaultEventMap>)[]Zero or more {EventTarget} or {EventEmitter} instances. If none are specified, nis set as the default max for all newly created {EventTarget} and {EventEmitter} objects.
 Returns void
StatictoWeb 
Properties
allowHalfOpen  
If false 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 existing
Duplex stream instance, but must be changed before the 'end' event is emitted.
Readonlyclosed
Is true after 'close' has been emitted.
destroyed
Is true after readable.destroy() has been called.
Readonlyerrored
Returns error if the stream has been destroyed with an error.
readable
Is true if it is safe to call read, which means
the stream has not been destroyed or emitted 'error' or 'end'.
ReadonlyreadableAborted 
Returns whether the stream was destroyed or errored before emitting 'end'.
ReadonlyreadableDidRead  
Returns whether 'data' has been emitted.
ReadonlyreadableEncoding 
Getter for the property encoding of a given Readable stream. The encoding property can be set using the setEncoding method.
ReadonlyreadableEnded 
Becomes true when 'end' event is emitted.
ReadonlyreadableFlowing 
This property reflects the current state of a Readable stream as described
in the Three states section.
ReadonlyreadableHighWaterMark   
Returns the value of highWaterMark passed when creating this Readable.
ReadonlyreadableLength 
This property contains the number of bytes (or objects) in the queue
ready to be read. The value provides introspection data regarding
the status of the highWaterMark.
ReadonlyreadableObjectMode  
Getter for the property objectMode of a given Readable stream.
Readonlywritable
Is true if it is safe to call writable.write(), which means
the stream has not been destroyed, errored, or ended.
ReadonlywritableAborted 
Returns whether the stream was destroyed or errored before emitting 'finish'.
ReadonlywritableCorked 
Number of times writable.uncork() needs to be
called in order to fully uncork the stream.
ReadonlywritableEnded 
Is true after writable.end() has been called. This property
does not indicate whether the data has been flushed, for this use writable.writableFinished instead.
ReadonlywritableFinished 
Is set to true immediately before the 'finish' event is emitted.
ReadonlywritableHighWaterMark   
Return the value of highWaterMark passed when creating this Writable.
ReadonlywritableLength 
This property contains the number of bytes (or objects) in the queue
ready to be written. The value provides introspection data regarding
the status of the highWaterMark.
ReadonlywritableNeedDrain  
Is true if the stream's buffer has been full and stream will emit 'drain'.
ReadonlywritableObjectMode  
Getter for the property objectMode of a given Writable stream.
StaticcaptureRejections 
Value: boolean
Change the default captureRejections option on all new EventEmitter objects.
Static ReadonlycaptureRejectionSymbol  
Value: Symbol.for('nodejs.rejection')
See how to write a custom rejection handler.
StaticdefaultMaxListeners  
By default, a maximum of 10 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 allEventEmitter 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 single
EventEmitter, the emitter.getMaxListeners() and emitter.setMaxListeners() methods can be used to
temporarily avoid this warning:
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'.
Static ReadonlyerrorMonitor 
This symbol shall be used to install a listener for only monitoring '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.
Calls
readable.destroy()with anAbortErrorand returns a promise that fulfills when the stream is finished.