WritableBase
admin/discounts.internal.WritableBase
The EventEmitter
class is defined and exposed by the node:events
module:
All EventEmitter
s emit the event 'newListener'
when new listeners are
added and 'removeListener'
when existing listeners are removed.
It supports the following option:
Since
v0.1.26
Implements
Implemented by
Properties
closed
booleanRequiredtrue
after 'close'
has been emitted. #### Since v18.0.0destroyed
booleanRequiredtrue
after writable.destroy()
has been called. #### Since v8.0.0writable
booleanRequiredtrue
if it is safe to call writable.write()
, which means the stream has not been destroyed, errored, or ended. #### Since v11.4.0writableCorked
numberRequiredwritable.uncork()
needs to be called in order to fully uncork the stream. #### Since v13.2.0, v12.16.0writableEnded
booleanRequiredtrue
after writable.end()
has been called. This property does not indicate whether the data has been flushed, for this use writable.writableFinished
instead. #### Since v12.9.0writableFinished
booleanRequiredtrue
immediately before the 'finish'
event is emitted. #### Since v12.6.0writableHighWaterMark
numberRequiredhighWaterMark
passed when creating this Writable
. #### Since v9.3.0writableLength
numberRequiredhighWaterMark
. #### Since v9.4.0writableNeedDrain
booleanRequiredtrue
if the stream's buffer has been full and stream will emit 'drain'
. #### Since v15.2.0, v14.17.0writableObjectMode
booleanRequiredobjectMode
of a given Writable
stream. #### Since v12.3.0Symbol.for('nodejs.rejection')
See how to write a custom rejection handler
. #### Since v13.4.0, v12.16.0captureRejections
booleanRequiredcaptureRejections
option on all new EventEmitter
objects. #### Since v13.4.0, v12.16.0defaultMaxListeners
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 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 allEventEmitter
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'
. #### Since v0.11.2'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. #### Since v13.6.0, v12.17.0Methods
_construct
Optional
_construct(callback
): void
Parameters
Returns
void
void
void_destroy
_destroy(error
, callback
): void
Parameters
Returns
void
void
void_final
_final(callback
): void
Parameters
Returns
void
void
void_write
_write(chunk
, encoding
, callback
): void
Parameters
Returns
void
void
void_writev
Optional
_writev(chunks
, callback
): void
Parameters
Returns
void
void
voidaddListener
addListener(event
, listener
): WritableBase
Event emitter The defined events on documents including:
- close
- drain
- error
- finish
- pipe
- unpipe
Parameters
event
"close"Requiredlistener
() => voidRequiredReturns
Implementation of
Overrides
addListener(event
, listener
): WritableBase
Parameters
event
"drain"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.addListener
Overrides
Stream.addListener
addListener(event
, listener
): WritableBase
Parameters
event
"error"RequiredReturns
Implementation of
NodeJS.WritableStream.addListener
Overrides
Stream.addListener
addListener(event
, listener
): WritableBase
Parameters
event
"finish"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.addListener
Overrides
Stream.addListener
addListener(event
, listener
): WritableBase
Parameters
event
"pipe"RequiredReturns
Implementation of
NodeJS.WritableStream.addListener
Overrides
Stream.addListener
addListener(event
, listener
): WritableBase
Parameters
event
"unpipe"RequiredReturns
Implementation of
NodeJS.WritableStream.addListener
Overrides
Stream.addListener
addListener(event
, listener
): WritableBase
Parameters
event
string | symbolRequiredlistener
(...args: any[]) => voidRequiredReturns
Implementation of
NodeJS.WritableStream.addListener
Overrides
Stream.addListener
cork
cork(): void
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
void
voidSince
v0.11.2
destroy
destroy(error?
): WritableBase
Destroy the stream. Optionally emit an 'error'
event, and emit a 'close'
event (unless emitClose
is set to false
). After this call, the writable
stream has ended and subsequent calls to write()
or end()
will result in
an ERR_STREAM_DESTROYED
error.
This is a destructive and immediate way to destroy a stream. Previous calls towrite()
may not have drained, and may trigger an ERR_STREAM_DESTROYED
error.
Use end()
instead of destroy if data should flush before close, or wait for
the 'drain'
event before destroying the stream.
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 writable._destroy()
.
Parameters
error
Error'error'
event.Returns
Since
v8.0.0
emit
emit(event
): boolean
Synchronously calls each of the listeners registered for the event namedeventName
, in the order they were registered, passing the supplied arguments
to each.
Returns true
if the event had listeners, false
otherwise.
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"RequiredReturns
boolean
boolean
booleanSince
v0.1.26
Implementation of
Overrides
emit(event
): boolean
Parameters
event
"drain"RequiredReturns
boolean
boolean
booleanImplementation of
NodeJS.WritableStream.emit
Overrides
Stream.emit
emit(event
, err
): boolean
Parameters
event
"error"RequiredReturns
boolean
boolean
booleanImplementation of
NodeJS.WritableStream.emit
Overrides
Stream.emit
emit(event
): boolean
Parameters
event
"finish"RequiredReturns
boolean
boolean
booleanImplementation of
NodeJS.WritableStream.emit
Overrides
Stream.emit
emit(event
, src
): boolean
Parameters
event
"pipe"RequiredReturns
boolean
boolean
booleanImplementation of
NodeJS.WritableStream.emit
Overrides
Stream.emit
emit(event
, src
): boolean
Parameters
event
"unpipe"RequiredReturns
boolean
boolean
booleanImplementation of
NodeJS.WritableStream.emit
Overrides
Stream.emit
emit(event
, ...args
): boolean
Parameters
event
string | symbolRequiredargs
any[]RequiredReturns
boolean
boolean
booleanImplementation of
NodeJS.WritableStream.emit
Overrides
Stream.emit
end
end(cb?
): WritableBase
Calling the writable.end()
method signals that no more data will be written
to the Writable
. The optional chunk
and encoding
arguments 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.
Parameters
cb
() => voidReturns
Since
v0.9.4
Implementation of
end(chunk
, cb?
): WritableBase
Parameters
chunk
anyRequiredcb
() => voidReturns
Implementation of
end(chunk
, encoding
, cb?
): WritableBase
Parameters
Returns
Implementation of
eventNames
eventNames(): (string
| symbol
)[]
Returns an array listing the events for which the emitter has registered
listeners. The values in the array are strings or Symbol
s.
Returns
(string
| symbol
)[]
(string \| symbol)[]
(string | symbol)[]Required
(string \| symbol)[]
(string | symbol)[]RequiredSince
v6.0.0
Implementation of
Inherited from
getMaxListeners
getMaxListeners(): number
Returns the current max listener value for the EventEmitter
which is either
set by emitter.setMaxListeners(n)
or defaults to defaultMaxListeners.
Returns
number
number
numberSince
v1.0.0
Implementation of
WritableStream.getMaxListeners
Inherited from
listenerCount
listenerCount(eventName
, listener?
): number
Returns the number of listeners listening for the event named eventName
.
If listener
is provided, it will return how many times the listener is found
in the list of the listeners of the event.
Parameters
eventName
string | symbolRequiredlistener
FunctionReturns
number
number
numberSince
v3.2.0
Implementation of
Inherited from
listeners
listeners(eventName
): Function
[]
Returns a copy of the array of listeners for the event named eventName
.
Parameters
eventName
string | symbolRequiredReturns
Function
[]
Function[]
Function[]RequiredSince
v0.1.26
Implementation of
Inherited from
off
off(eventName
, listener
): WritableBase
Alias for emitter.removeListener()
.
Parameters
eventName
string | symbolRequiredlistener
(...args: any[]) => voidRequiredReturns
Since
v10.0.0
Implementation of
Inherited from
on
on(event
, listener
): WritableBase
Adds the listener
function to the end of the listeners array for the
event named eventName
. No checks are made to see if the listener
has
already been added. Multiple calls passing the same combination of eventName
and listener
will result in the listener
being added, and called, multiple
times.
Returns a reference to the EventEmitter
, so that calls can be chained.
By default, event listeners are invoked in the order they are added. Theemitter.prependListener()
method can be used as an alternative to add the
event listener to the beginning of the listeners array.
Parameters
event
"close"Requiredlistener
() => voidRequiredReturns
Since
v0.1.101
Implementation of
Overrides
on(event
, listener
): WritableBase
Parameters
event
"drain"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.on
Overrides
Stream.on
on(event
, listener
): WritableBase
Parameters
event
"error"RequiredReturns
Implementation of
NodeJS.WritableStream.on
Overrides
Stream.on
on(event
, listener
): WritableBase
Parameters
event
"finish"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.on
Overrides
Stream.on
on(event
, listener
): WritableBase
Parameters
event
"pipe"RequiredReturns
Implementation of
NodeJS.WritableStream.on
Overrides
Stream.on
on(event
, listener
): WritableBase
Parameters
event
"unpipe"RequiredReturns
Implementation of
NodeJS.WritableStream.on
Overrides
Stream.on
on(event
, listener
): WritableBase
Parameters
event
string | symbolRequiredlistener
(...args: any[]) => voidRequiredReturns
Implementation of
NodeJS.WritableStream.on
Overrides
Stream.on
once
once(event
, listener
): WritableBase
Adds a one-timelistener
function for the event named eventName
. The
next time eventName
is triggered, this listener is removed and then invoked.
Returns a reference to the EventEmitter
, so that calls can be chained.
By default, event listeners are invoked in the order they are added. Theemitter.prependOnceListener()
method can be used as an alternative to add the
event listener to the beginning of the listeners array.
Parameters
event
"close"Requiredlistener
() => voidRequiredReturns
Since
v0.3.0
Implementation of
Overrides
once(event
, listener
): WritableBase
Parameters
event
"drain"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.once
Overrides
Stream.once
once(event
, listener
): WritableBase
Parameters
event
"error"RequiredReturns
Implementation of
NodeJS.WritableStream.once
Overrides
Stream.once
once(event
, listener
): WritableBase
Parameters
event
"finish"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.once
Overrides
Stream.once
once(event
, listener
): WritableBase
Parameters
event
"pipe"RequiredReturns
Implementation of
NodeJS.WritableStream.once
Overrides
Stream.once
once(event
, listener
): WritableBase
Parameters
event
"unpipe"RequiredReturns
Implementation of
NodeJS.WritableStream.once
Overrides
Stream.once
once(event
, listener
): WritableBase
Parameters
event
string | symbolRequiredlistener
(...args: any[]) => voidRequiredReturns
Implementation of
NodeJS.WritableStream.once
Overrides
Stream.once
pipe
pipe<T
>(destination
, options?
): T
Parameters
destination
TRequiredoptions
objectoptions.end
booleanReturns
T
Inherited from
prependListener
prependListener(event
, listener
): WritableBase
Adds the listener
function to the beginning of the listeners array for the
event named eventName
. No checks are made to see if the listener
has
already been added. Multiple calls passing the same combination of eventName
and listener
will result in the listener
being added, and called, multiple
times.
Returns a reference to the EventEmitter
, so that calls can be chained.
Parameters
event
"close"Requiredlistener
() => voidRequiredReturns
Since
v6.0.0
Implementation of
WritableStream.prependListener
Overrides
prependListener(event
, listener
): WritableBase
Parameters
event
"drain"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.prependListener
Overrides
Stream.prependListener
prependListener(event
, listener
): WritableBase
Parameters
event
"error"RequiredReturns
Implementation of
NodeJS.WritableStream.prependListener
Overrides
Stream.prependListener
prependListener(event
, listener
): WritableBase
Parameters
event
"finish"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.prependListener
Overrides
Stream.prependListener
prependListener(event
, listener
): WritableBase
Parameters
event
"pipe"RequiredReturns
Implementation of
NodeJS.WritableStream.prependListener
Overrides
Stream.prependListener
prependListener(event
, listener
): WritableBase
Parameters
event
"unpipe"RequiredReturns
Implementation of
NodeJS.WritableStream.prependListener
Overrides
Stream.prependListener
prependListener(event
, listener
): WritableBase
Parameters
event
string | symbolRequiredlistener
(...args: any[]) => voidRequiredReturns
Implementation of
NodeJS.WritableStream.prependListener
Overrides
Stream.prependListener
prependOnceListener
prependOnceListener(event
, listener
): WritableBase
Adds a one-timelistener
function for the event named eventName
to the beginning of the listeners array. The next time eventName
is triggered, this
listener is removed, and then invoked.
Returns a reference to the EventEmitter
, so that calls can be chained.
Parameters
event
"close"Requiredlistener
() => voidRequiredReturns
Since
v6.0.0
Implementation of
WritableStream.prependOnceListener
Overrides
prependOnceListener(event
, listener
): WritableBase
Parameters
event
"drain"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.prependOnceListener
Overrides
Stream.prependOnceListener
prependOnceListener(event
, listener
): WritableBase
Parameters
event
"error"RequiredReturns
Implementation of
NodeJS.WritableStream.prependOnceListener
Overrides
Stream.prependOnceListener
prependOnceListener(event
, listener
): WritableBase
Parameters
event
"finish"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.prependOnceListener
Overrides
Stream.prependOnceListener
prependOnceListener(event
, listener
): WritableBase
Parameters
event
"pipe"RequiredReturns
Implementation of
NodeJS.WritableStream.prependOnceListener
Overrides
Stream.prependOnceListener
prependOnceListener(event
, listener
): WritableBase
Parameters
event
"unpipe"RequiredReturns
Implementation of
NodeJS.WritableStream.prependOnceListener
Overrides
Stream.prependOnceListener
prependOnceListener(event
, listener
): WritableBase
Parameters
event
string | symbolRequiredlistener
(...args: any[]) => voidRequiredReturns
Implementation of
NodeJS.WritableStream.prependOnceListener
Overrides
Stream.prependOnceListener
rawListeners
rawListeners(eventName
): Function
[]
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');
Parameters
eventName
string | symbolRequiredReturns
Function
[]
Function[]
Function[]RequiredSince
v9.4.0
Implementation of
Inherited from
removeAllListeners
removeAllListeners(event?
): WritableBase
Removes all listeners, or those of the specified eventName
.
It is bad practice to remove listeners added elsewhere in the code,
particularly when the EventEmitter
instance 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
event
string | symbolReturns
Since
v0.1.26
Implementation of
WritableStream.removeAllListeners
Inherited from
removeListener
removeListener(event
, listener
): WritableBase
Removes the specified listener
from the listener array for the event namedeventName
.
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 anyremoveListener()
or removeAllListeners()
calls after emitting and before the last listener finishes execution
will not remove them fromemit()
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:
Returns a reference to the EventEmitter
, so that calls can be chained.
Parameters
event
"close"Requiredlistener
() => voidRequiredReturns
Since
v0.1.26
Implementation of
Overrides
removeListener(event
, listener
): WritableBase
Parameters
event
"drain"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.removeListener
Overrides
Stream.removeListener
removeListener(event
, listener
): WritableBase
Parameters
event
"error"RequiredReturns
Implementation of
NodeJS.WritableStream.removeListener
Overrides
Stream.removeListener
removeListener(event
, listener
): WritableBase
Parameters
event
"finish"Requiredlistener
() => voidRequiredReturns
Implementation of
NodeJS.WritableStream.removeListener
Overrides
Stream.removeListener
removeListener(event
, listener
): WritableBase
Parameters
event
"pipe"RequiredReturns
Implementation of
NodeJS.WritableStream.removeListener
Overrides
Stream.removeListener
removeListener(event
, listener
): WritableBase
Parameters
event
"unpipe"RequiredReturns
Implementation of
NodeJS.WritableStream.removeListener
Overrides
Stream.removeListener
removeListener(event
, listener
): WritableBase
Parameters
event
string | symbolRequiredlistener
(...args: any[]) => voidRequiredReturns
Implementation of
NodeJS.WritableStream.removeListener
Overrides
Stream.removeListener
setDefaultEncoding
setDefaultEncoding(encoding
): WritableBase
The writable.setDefaultEncoding()
method sets the default encoding
for a Writable
stream.
Parameters
Returns
Since
v0.11.15
setMaxListeners
setMaxListeners(n
): WritableBase
By default EventEmitter
s will print a warning if more than 10
listeners 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 EventEmitter
instance. The value can be set toInfinity
(or 0
) to indicate an unlimited number of listeners.
Returns a reference to the EventEmitter
, so that calls can be chained.
Parameters
n
numberRequiredReturns
Since
v0.3.5
Implementation of
WritableStream.setMaxListeners
Inherited from
uncork
uncork(): void
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()
usingprocess.nextTick()
. Doing so allows batching of allwritable.write()
calls that occur within a given Node.js event
loop phase.
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.
See also: writable.cork()
.
Returns
void
void
voidSince
v0.11.2
write
write(chunk
, callback?
): boolean
The writable.write()
method writes some data to the stream, and calls the
supplied callback
once the data has been fully handled. If an error
occurs, the callback
will be called with the error as its
first argument. The callback
is called asynchronously and before 'error'
is
emitted.
The return value is true
if the internal buffer is less than thehighWaterMark
configured when the stream was created after admitting chunk
.
If false
is 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 Transform
streams 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 Readable
and use pipe. However, if calling write()
is preferred, it is
possible to respect backpressure and avoid memory issues using the 'drain'
event:
A Writable
stream in object mode will always ignore the encoding
argument.
Parameters
chunk
anyRequiredchunk
must be a string, Buffer
or Uint8Array
. For object mode streams, chunk
may be any JavaScript value other than null
.callback
(error: undefined | null | Error) => voidReturns
boolean
boolean
booleanfalse
if the stream wishes for the calling code to wait for the 'drain'
event to be emitted before continuing to write additional data; otherwise true
.Since
v0.9.4
Implementation of
write(chunk
, encoding
, callback?
): boolean
Parameters
Returns
boolean
boolean
booleanImplementation of
getEventListeners
Static
getEventListeners(emitter
, name
): Function
[]
Returns a copy of the array of listeners for the event named eventName
.
For EventEmitter
s this behaves exactly the same as calling .listeners
on
the emitter.
For EventTarget
s 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
name
string | symbolRequiredReturns
Function
[]
Function[]
Function[]RequiredSince
v15.2.0, v14.17.0
Inherited from
listenerCount
Static
listenerCount(emitter
, eventName
): number
A class method that returns the number of listeners for the given eventName
registered on the given emitter
.
Parameters
eventName
string | symbolRequiredReturns
number
number
numberSince
v0.9.12
Deprecated
Since v3.2.0 - Use listenerCount
instead.
Inherited from
on
Static
on(emitter
, eventName
, options?
): AsyncIterableIterator
<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 here
Returns an AsyncIterator
that iterates eventName
events. It will throw
if the EventEmitter
emits 'error'
. It removes all listeners when
exiting the loop. The value
returned by each iteration is an array
composed of the emitted event arguments.
An AbortSignal
can 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());
Parameters
Returns
that iterates eventName
events emitted by the emitter
eventName
events emitted by the emitter
Since
v13.6.0, v12.16.0
Inherited from
once
Static
once(emitter
, eventName
, options?
): Promise
<any
[]>
Creates a Promise
that is fulfilled when the EventEmitter
emits the given
event or that is rejected if the EventEmitter
emits 'error'
while waiting.
The Promise
will 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 when events.once()
is used to wait for another event. If events.once()
is used to wait for the
'error'
event itself, then it is treated as any other kind of event without
special handling:
An AbortSignal
can 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
Returns
Promise
<any
[]>
Promise
Promise<any[]>Required
Promise
Promise<any[]>RequiredSince
v11.13.0, v10.16.0
Inherited from
Static
once(emitter
, eventName
, options?
): Promise
<any
[]>
Parameters
Returns
Promise
<any
[]>
Promise
Promise<any[]>Required
Promise
Promise<any[]>RequiredInherited from
setMaxListeners
Static
setMaxListeners(n?
, ...eventTargets
): void
Parameters
n
numberEventTarget
event.Returns
void
void
voidSince
v15.4.0