Search the reference...
/
BuildDocsReferenceGuidesBlogDiscord/node:worker_threads/WorkerM[Symbol.asyncDispose]M[events.captureRejectionSymbol]MaddListenerCoconstructorMcpuUsageMemitMeventNamesMgetHeapSnapshotMgetHeapStatisticsMgetMaxListenersMlistenerCountMlistenersMoffMonMoncePperformanceMpostMessageMprependListenerMprependOnceListenerMrawListenersMrefMremoveAllListenersMremoveListenerPresourceLimitsMsetMaxListenersMstartCpuProfileMstartHeapProfilePstderrPstdinPstdoutMterminatePthreadIdPthreadNameMunrefclass
worker_threads.Worker { console.log('received:', value); }); } else { parentPort.once('message', (value) => { assert(value.hereIsYourPort instanceof MessagePort); value.hereIsYourPort.postMessage('the worker is sending this'); value.hereIsYourPort.close(); }); } ```" data-algolia-static="false" data-algolia-merged="false" data-type="Class">class WorkerThe Worker class represents an independent JavaScript execution thread. Most Node.js APIs are available inside of it.Notable differences inside a Worker environment are:The process.stdin, process.stdout, and process.stderr streams may be redirected by the parent thread.The import { isMainThread } from 'node:worker_threads' variable is set to false.The import { parentPort } from 'node:worker_threads' message port is available.process.exit() does not stop the whole program, just the single thread, and process.abort() is not available.process.chdir() and process methods that set group or user ids are not available.process.env is a copy of the parent thread's environment variables, unless otherwise specified. Changes to one copy are not visible in other threads, and are not visible to native add-ons (unless worker.SHARE_ENV is passed as the env option to the Worker constructor). On Windows, unlike the main thread, a copy of the environment variables operates in a case-sensitive manner.process.title cannot be modified.Signals are not delivered through process.on('...').Execution may stop at any point as a result of worker.terminate() being invoked.IPC channels from parent processes are not accessible.The trace_events module is not supported.Native add-ons can only be loaded from multiple threads if they fulfill certain conditions.Creating Worker instances inside of other Workers is possible.Like Web Workers and the node:cluster module, two-way communication can be achieved through inter-thread message passing. Internally, a Worker has a built-in pair of MessagePort s that are already associated with each other when the Worker is created. While the MessagePort object on the parent side is not directly exposed, its functionalities are exposed through worker.postMessage() and the worker.on('message') event on the Worker object for the parent thread.To create custom messaging channels (which is encouraged over using the default global channel because it facilitates separation of concerns), users can create a MessageChannel object on either thread and pass one of theMessagePorts on that MessageChannel to the other thread through a pre-existing channel, such as the global one.See port.postMessage() for more information on how messages are passed, and what kind of JavaScript values can be successfully transported through the thread barrier.import assert from 'node:assert'; import { Worker, MessageChannel, MessagePort, isMainThread, parentPort, } from 'node:worker_threads'; if (isMainThread) { const worker = new Worker(__filename); const subChannel = new MessageChannel(); worker.postMessage({ hereIsYourPort: subChannel.port1 }, [subChannel.port1]); subChannel.port2.on('message', (value) => { console.log('received:', value); }); } else { parentPort.once('message', (value) => { assert(value.hereIsYourPort instanceof MessagePort); value.hereIsYourPort.postMessage('the worker is sending this'); value.hereIsYourPort.close(); }); } readonly performance: WorkerPerformanceAn object that can be used to query performance information from a worker instance. Similar to perf_hooks.performance.readonly resourceLimits?: ResourceLimitsProvides the set of JS engine resource constraints for this Worker thread. If the resourceLimits option was passed to the Worker constructor, this matches its values.If the worker has stopped, the return value is an empty object.readonly stderr: ReadableThis is a readable stream which contains data written to process.stderr inside the worker thread. If stderr: true was not passed to the Worker constructor, then data is piped to the parent thread's process.stderr stream.readonly stdin: null | WritableIf stdin: true was passed to the Worker constructor, this is a writable stream. The data written to this stream will be made available in the worker thread as process.stdin.readonly stdout: ReadableThis is a readable stream which contains data written to process.stdout inside the worker thread. If stdout: true was not passed to the Worker constructor, then data is piped to the parent thread's process.stdout stream.readonly threadId: numberAn integer identifier for the referenced thread. Inside the worker thread, it is available as import { threadId } from 'node:worker_threads'. This value is unique for each Worker instance inside a single process.readonly threadName: null | stringA string identifier for the referenced thread or null if the thread is not running. Inside the worker thread, it is available as require('node:worker_threads').threadName.[Symbol.asyncDispose](): Promisevoid>;Calls worker.terminate() when the dispose scope is exited.async function example() { await using worker = new Worker('for (;;) {}', { eval: true }); // Worker is automatically terminate when the scope is exited. } [events.captureRejectionSymbol](error: Error,event: string | symbol,...args: any[]): void;The Symbol.for('nodejs.rejection') method is called in case a promise rejection happens when emitting an event and captureRejections is enabled on the emitter. It is possible to use events.captureRejectionSymbol in place of Symbol.for('nodejs.rejection').import { EventEmitter, captureRejectionSymbol } from 'node:events'; class MyClass extends EventEmitter { constructor() { super({ captureRejections: true }); } [captureRejectionSymbol](err, event, ...args) { console.log('rejection happened for', event, 'with', err, ...args); this.destroy(err); } destroy(err) { // Tear the resource down here. } } addListenerE extends keyof WorkerEventMap>(eventName: E,listener: (...args: WorkerEventMap[E]) => void): this;Alias for emitter.on(eventName, listener).addListener(eventName: string | symbol,listener: (...args: any[]) => void): this;Alias for emitter.on(eventName, listener).cpuUsage(prev?: CpuUsage): PromiseCpuUsage>;This method returns a Promise that will resolve to an object identical to process.threadCpuUsage(), or reject with an ERR_WORKER_NOT_RUNNING error if the worker is no longer running. This methods allows the statistics to be observed from outside the actual thread.emitE extends keyof WorkerEventMap>(eventName: E,...args: WorkerEventMap[E]): boolean;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 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 emit(eventName: string | symbol,...args: any[]): boolean;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 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 {}); myEE.on('bar', () => {}); const sym = Symbol('symbol'); myEE.on(sym, () => {}); console.log(myEE.eventNames()); // Prints: [ 'foo', 'bar', Symbol(symbol) ] ```" data-algolia-static="false" data-algolia-merged="false" data-type="Method">eventNames(): string | symbol[];Returns an array listing the events for which the emitter has registered listeners.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) ] getHeapSnapshot(): PromiseReadable>;Returns a readable stream for a V8 snapshot of the current state of the Worker. See v8.getHeapSnapshot() for more details.If the Worker thread is no longer running, which may occur before the 'exit' event is emitted, the returned Promise is rejected immediately with an ERR_WORKER_NOT_RUNNING error.@returnsA promise for a Readable Stream containing a V8 heap snapshotgetHeapStatistics(): PromiseHeapInfo>;This method returns a Promise that will resolve to an object identical to v8.getHeapStatistics(), or reject with an ERR_WORKER_NOT_RUNNING error if the worker is no longer running. This methods allows the statistics to be observed from outside the actual thread.getMaxListeners(): number;Returns the current max listener value for the EventEmitter which is either set by emitter.setMaxListeners(n) or defaults to events.defaultMaxListeners.listenerCountE extends keyof WorkerEventMap>(eventName: E,listener?: (...args: WorkerEventMap[E]) => void): 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.@param eventNameThe name of the event being listened for@param listenerThe event handler functionlistenerCount(eventName: string | symbol,listener?: (...args: any[]) => void): 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.@param eventNameThe name of the event being listened for@param listenerThe event handler function { console.log('someone connected!'); }); console.log(util.inspect(server.listeners('connection'))); // Prints: [ [Function] ] ```" data-algolia-static="false" data-algolia-merged="false" data-type="Method">listenersE extends keyof WorkerEventMap>(eventName: E): (...args: WorkerEventMap[E]) => void[];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] ] listeners(eventName: string | symbol): (...args: any[]) => void[];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] ] offE extends keyof WorkerEventMap>(eventName: E,listener: (...args: WorkerEventMap[E]) => void): this;Alias for emitter.removeListener().off(eventName: string | symbol,listener: (...args: any[]) => void): this;Alias for emitter.removeListener(). { 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. ```js 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 ```" data-algolia-static="false" data-algolia-merged="false" data-type="Method">onE extends keyof WorkerEventMap>(eventName: E,listener: (...args: WorkerEventMap[E]) => void): this;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.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 @param eventNameThe name of the event.@param listenerThe callback functionon(eventName: string | symbol,listener: (...args: any[]) => void): this;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.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 @param eventNameThe name of the event.@param listenerThe callback function { 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. ```js 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 ```" data-algolia-static="false" data-algolia-merged="false" data-type="Method">onceE extends keyof WorkerEventMap>(eventName: E,listener: (...args: WorkerEventMap[E]) => void): this;Adds a one-time listener function for the event named eventName. The next time eventName is 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 @param eventNameThe name of the event.@param listenerThe callback functiononce(eventName: string | symbol,listener: (...args: any[]) => void): this;Adds a one-time listener function for the event named eventName. The next time eventName is 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 @param eventNameThe name of the event.@param listenerThe callback functionpostMessage(value: any,transferList?: readonly Transferable[]): void;Send a message to the worker that is received via require('node:worker_threads').parentPort.on('message'). See port.postMessage() for more details. { console.log('someone connected!'); }); ``` Returns a reference to the `EventEmitter`, so that calls can be chained." data-algolia-static="false" data-algolia-merged="false" data-type="Method">prependListenerE extends keyof WorkerEventMap>(eventName: E,listener: (...args: WorkerEventMap[E]) => void): this;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.server.prependListener('connection', (stream) => { console.log('someone connected!'); }); Returns a reference to the EventEmitter, so that calls can be chained.@param eventNameThe name of the event.@param listenerThe callback functionprependListener(eventName: string | symbol,listener: (...args: any[]) => void): this;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.server.prependListener('connection', (stream) => { console.log('someone connected!'); }); Returns a reference to the EventEmitter, so that calls can be chained.@param eventNameThe name of the event.@param listenerThe callback function { console.log('Ah, we have our first user!'); }); ``` Returns a reference to the `EventEmitter`, so that calls can be chained." data-algolia-static="false" data-algolia-merged="false" data-type="Method">prependOnceListenerE extends keyof WorkerEventMap>(eventName: E,listener: (...args: WorkerEventMap[E]) => void): this;Adds a one-time listener 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.server.prependOnceListener('connection', (stream) => { console.log('Ah, we have our first user!'); }); Returns a reference to the EventEmitter, so that calls can be chained.@param eventNameThe name of the event.@param listenerThe callback functionprependOnceListener(eventName: string | symbol,listener: (...args: any[]) => void): this;Adds a one-time listener 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.server.prependOnceListener('connection', (stream) => { console.log('Ah, we have our first user!'); }); Returns a reference to the EventEmitter, so that calls can be chained.@param eventNameThe name of the event.@param listenerThe callback function 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'); ```" data-algolia-static="false" data-algolia-merged="false" data-type="Method">rawListenersE extends keyof WorkerEventMap>(eventName: E): (...args: WorkerEventMap[E]) => void[];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'); rawListeners(eventName: string | symbol): (...args: any[]) => void[];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'); ref(): void;Opposite of unref(), calling ref() on a previously unref()ed worker does not let the program exit if it's the only active handle left (the default behavior). If the worker is ref()ed, calling ref() again has no effect.removeAllListenersE extends keyof WorkerEventMap>(eventName?: E): this;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.removeAllListeners(eventName?: string | symbol): this;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. { 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. ```js 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 indexes 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: ```js 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." data-algolia-static="false" data-algolia-merged="false" data-type="Method">removeListenerE extends keyof WorkerEventMap>(eventName: E,listener: (...args: WorkerEventMap[E]) => void): this;Removes the specified listener from 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 indexes 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.removeListener(eventName: string | symbol,listener: (...args: any[]) => void): this;Removes the specified listener from 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 indexes 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.setMaxListeners(n: number): this;By default EventEmitters 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 to Infinity (or 0) to indicate an unlimited number of listeners.Returns a reference to the EventEmitter, so that calls can be chained. {}); `, { eval: true }); worker.on('online', async () => { const handle = await worker.startCpuProfile(); const profile = await handle.stop(); console.log(profile); worker.terminate(); }); ``` `await using` example. ```js const { Worker } = require('node:worker_threads'); const w = new Worker(` const { parentPort } = require('node:worker_threads'); parentPort.on('message', () => {}); `, { eval: true }); w.on('online', async () => { // Stop profile automatically when return and profile will be discarded await using handle = await w.startCpuProfile(); }); ```" data-algolia-static="false" data-algolia-merged="false" data-type="Method">startCpuProfile(): PromiseCPUProfileHandle>;Starting a CPU profile then return a Promise that fulfills with an error or an CPUProfileHandle object. This API supports await using syntax.const { Worker } = require('node:worker_threads'); const worker = new Worker(` const { parentPort } = require('worker_threads'); parentPort.on('message', () => {}); `, { eval: true }); worker.on('online', async () => { const handle = await worker.startCpuProfile(); const profile = await handle.stop(); console.log(profile); worker.terminate(); }); await using example.const { Worker } = require('node:worker_threads'); const w = new Worker(` const { parentPort } = require('node:worker_threads'); parentPort.on('message', () => {}); `, { eval: true }); w.on('online', async () => { // Stop profile automatically when return and profile will be discarded await using handle = await w.startCpuProfile(); }); {}); `, { eval: true }); worker.on('online', async () => { const handle = await worker.startHeapProfile(); const profile = await handle.stop(); console.log(profile); worker.terminate(); }); ``` `await using` example. ```js const { Worker } = require('node:worker_threads'); const w = new Worker(` const { parentPort } = require('node:worker_threads'); parentPort.on('message', () => {}); `, { eval: true }); w.on('online', async () => { // Stop profile automatically when return and profile will be discarded await using handle = await w.startHeapProfile(); }); ```" data-algolia-static="false" data-algolia-merged="false" data-type="Method">startHeapProfile(): PromiseHeapProfileHandle>;Starting a Heap profile then return a Promise that fulfills with an error or an HeapProfileHandle object. This API supports await using syntax.const { Worker } = require('node:worker_threads'); const worker = new Worker(` const { parentPort } = require('worker_threads'); parentPort.on('message', () => {}); `, { eval: true }); worker.on('online', async () => { const handle = await worker.startHeapProfile(); const profile = await handle.stop(); console.log(profile); worker.terminate(); }); await using example.const { Worker } = require('node:worker_threads'); const w = new Worker(` const { parentPort } = require('node:worker_threads'); parentPort.on('message', () => {}); `, { eval: true }); w.on('online', async () => { // Stop profile automatically when return and profile will be discarded await using handle = await w.startHeapProfile(); }); terminate(): Promisenumber>;Stop all JavaScript execution in the worker thread as soon as possible. Returns a Promise for the exit code that is fulfilled when the 'exit' event is emitted.unref(): void;Calling unref() on a worker allows the thread to exit if this is the only active handle in the event system. If the worker is already unref()ed calling unref() again has no effect.Resources
ReferenceDocsGuidesDiscordMerch StoreGitHubBlogToolkit
RuntimePackage managerTest runnerBundlerPackage runnerProject
Bun 1.0Bun 1.1Bun 1.2Bun 1.3RoadmapContributingLicenseBaked with ❤️ in San FranciscoWe're hiring →智能索引记录
-
2026-03-02 15:50:31
游戏娱乐
成功
标题:beat·365(中国) - 官方网站
简介:⚽️Beat365官方网站即时软件已成为中国网民网上娱乐的主要方式,Beat365官方网站这里聚集了全球各个国家的游戏玩
-
2026-03-03 04:53:18
综合导航
成功
标题:Which States Have the Lowest Gas Prices?
简介:AAA: 38 states posting averages below $2 per gallon; 17 belo
-
2026-03-02 16:27:04
综合导航
成功
标题:Alderman. World English Historical Dictionary
简介:Alderman. World English Historical Dictionary
-
2026-03-02 17:12:04
数码科技
成功
标题:阿里云-计算,为了无法计算的价值
简介:阿里云——阿里巴巴集团旗下全球领先的云计算及人工智能科技公司之一。提供全栈云服务,包括弹性计算、高性能数据库、网络与存储
-
2026-03-02 20:23:26
综合导航
成功
标题:绝品女仙最新章节_第八十五章 该死的白煜第1页_绝品女仙免费章节_恋上你看书网
简介:第八十五章 该死的白煜第1页_绝品女仙_安筱楼_恋上你看书网
-
2026-03-02 22:47:32
游戏娱乐
成功
标题:我掀起了亡灵天灾全文阅读(午韦壬),我掀起了亡灵天灾的结局_我掀起了亡灵天灾全本,完结,全集阅读,无弹窗广告_小说在线阅读,新笔趣阁(56xu.com)
简介:新笔趣阁免费提供午韦壬写的游戏竞技经典作品我掀起了亡灵天灾,我掀起了亡灵天灾全文阅读,我掀起了亡灵天灾完结,全本,全集阅
-
2026-03-02 20:36:58
综合导航
成功
标题:18禁妖怪诊所by甜甜t最新章节_9441òùщēииρмē 009 雄性资本第1页_18禁妖怪诊所by甜甜t免费阅读_恋上你看书网
简介:9441òùщēииρмē 009 雄性资本第1页_18禁妖怪诊所by甜甜t_甜甜T_恋上你看书网
-
2026-03-02 23:01:59
综合导航
成功
标题:5 INFLUENCERS 5 RECIPES 5 CHALLENGES LG Global
简介:To demonstrate the unique, innovative features of LG
-
2026-03-02 22:00:03
综合导航
成功
标题:PLC-Glasfaser-Splitter, PON-Splitter - FS Deutschland
简介:PLC-Glasfaser-Splitter von FS mit niedriger IL&PDL und hoher
-
2026-03-03 03:44:08
综合导航
成功
标题:宁德银典物业招聘_宁德银典物业管理服务有限公司招聘_电话_地址 _【官方】
简介:宁德银典物业招聘,宁德银典物业管理服务有限公司招聘,公司在宁德市蕉城区漳湾镇新港路1号(宁德新能源旁)冠云轩小区6号楼2
-
2026-03-02 23:07:22
综合导航
成功
标题:Anthony Trollope (1815-1882). The Reader's Biographical Encyclopaedia. 1922
简介:Anthony Trollope (1815-1882). The Reader
-
2026-03-02 12:40:04
综合导航
成功
标题:Home Western Corrugated Design Club Store Displays & Packaging 10035 Geary Ave Santa Fe Springs, CA 90670
简介:WCD WCDFulfillment in Santa Fe Springs, CA offers premier
-
2026-03-02 17:21:55
综合导航
成功
标题:Schaeffler Germany
简介:Schaeffler has been driving forward groundbreaking invention
-
2026-03-03 05:20:02
综合导航
成功
标题:Tricky Falling Ball - Play Tricky Falling Ball Game Online Free
简介:Play Tricky Falling Ball game online for free on YAD. The ga
-
2026-03-02 22:46:46
游戏娱乐
成功
标题:快速化妆,快速化妆小游戏,4399小游戏 www.4399.com
简介:快速化妆在线玩,快速化妆下载, 快速化妆攻略秘籍.更多快速化妆游戏尽在4399小游戏,好玩记得告诉你的朋友哦!
-
2026-03-03 03:51:59
教育培训
成功
标题:【优秀】爷爷作文8篇
简介:在平日的学习、工作和生活里,大家一定都接触过作文吧,作文是人们把记忆中所存储的有关知识、经验和思想用书面形式表达出来的记
-
2026-03-03 06:49:07
综合导航
成功
标题:Creatieve tools - Alle accessoires - Apple (BE)
简介:Ontdek hoe je je artistieke vaardigheden maximaal benut met
-
2026-03-02 15:19:15
教育培训
成功
标题:(经典)告诉你一件新鲜事作文
简介:在现实生活或工作学习中,说到作文,大家肯定都不陌生吧,借助作文可以提高我们的语言组织能力。你所见过的作文是什么样的呢?以
-
2026-03-03 05:20:49
图片素材
成功
标题:见谅的作文400字 描写见谅的作文 关于见谅的作文-作文网
简介:作文网精选关于见谅的400字作文,包含见谅的作文素材,关于见谅的作文题目,以见谅为话题的400字作文大全,作文网原创名师
-
2026-03-02 21:57:27
综合导航
成功
标题:TRE008 - StrongShop
简介:Item Name : TRE008 Description : 15
-
2026-03-02 21:56:45
综合导航
成功
标题:WTB eibach or st springs [Archive] - Toyota MR2 Message Board
简介:Looking for some used performance springs in decent shape. W
-
2026-03-02 22:55:28
综合导航
成功
标题:è¿æ²»çæ¼é³_è¿æ²»çææ_è¿æ²»çç¹ä½_è¯ç»ç½
简介:è¯ç»ç½è¿æ²»é¢é,ä»ç»è¿æ²»,è¿æ²»çæ¼é³,è¿æ²»æ¯
-
2026-03-02 22:05:35
教育培训
成功
标题:华侨大学金融硕士初试备考经验分享-高顿教育
简介:写在前面:考研难吗?难也不难。考研是一个长期坚持的过程,不是三分钟热度就可以成功的。作为高顿的资深小编,在夏季真正到来之
-
2026-03-02 16:26:16
职场办公
成功
标题:2022年公司行政工作计划-果果圈模板
简介:作为公司的行政人事,对本年度的工作做出计划有利于我们在之后的工作中有一定的目标和方向。下面是小编给大家带来的2022年公
-
2026-03-02 20:16:55
综合导航
成功
标题:京东(JD.COM)-正品低价、品质保障、配送及时、轻松购物!
简介:京东JD.COM-专业的综合网上购物商城,为您提供正品低价的购物选择、优质便捷的服务体验。商品来自全球数十万品牌商家,囊
-
2026-03-02 17:40:35
综合导航
成功
标题:WTB: 1ZZ COIL pigtail connectors [Archive] - Toyota MR2 Message Board
简介:i don
-
2026-03-02 17:38:14
综合导航
成功
标题:AI智能索引 - AI智能索引
简介:AI智能索引 - 提供全网公开链接智能索引服务,快速访问目标内容,支持分类筛选和智能导航
-
2026-03-02 22:28:03
综合导航
成功
标题:Industries
简介:Our industry-focused network is designed to anticipate and a
-
2026-03-03 06:29:48
综合导航
成功
标题:于阗是什么意思_于阗的词语解释-雄安文学网
简介:于阗是什么意思?雄安文学网为您提供于阗的的意思解释,解读于阗的解释含义,包括基本解释和详细解释等。
-
2026-03-02 22:00:53
游戏娱乐
成功
标题:绝世仙王美人进阶数据是多少 美人系统怎么玩_欢乐园游戏
简介:绝世仙王拥有很多进阶玩法,其中包括美人在内。那么绝世仙王美人进阶数据是多少?美人系统怎么玩?在绝世仙王的美女系统,实际上