StaticcaptureValue: boolean
Change the default captureRejections option on all new
EventEmitter objects.
Static ReadonlycaptureValue: Symbol.for('nodejs.rejection')
See how to write a custom rejection handler.
Staticdefault
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 Readonlyerror
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.
Optional[captureUnified analyze - consolidate multiple Pike operations in one request.
Performs compilation and tokenization once, then distributes results to all requested operation types. More efficient than calling parse(), introspect(), and analyzeUninitialized() separately.
Supports partial success - each requested operation appears in either result or failures, never both. Use failures?.[operation] for O(1) lookup.
Pike source code to analyze.
Which operations to perform (at least one required).
Optionalfilename:
string
Optional filename for error messages.
OptionaldocumentVersion:
number
Optional LSP document version (for cache invalidation). If provided, cache uses LSP version instead of file stat.
Analyze response with result/failures structure and performance timing.
const response = await bridge.analyze(
'class Foo { int bar() { return 5; } }',
'example.pike',
['parse', 'introspect', 'diagnostics']
);
// Check for specific operation success
if (response.result?.introspect) {
console.log(response.result.introspect.symbols);
}
// Check for specific operation failure
if (response.failures?.diagnostics) {
console.error(response.failures.diagnostics.message);
}
// Access performance timing
console.log(`Compilation took ${response._perf?.compilation_ms}ms`);
Analyze Pike code for uninitialized variable usage.
Performs dataflow analysis to detect variables that may be used before being initialized. Only warns for types where uninitialized access would cause runtime errors (string, array, mapping, etc.), not for int/float which auto-initialize to 0.
Pike source code to analyze.
Optionalfilename:
string
Optional filename for error messages.
Analysis result with diagnostics for uninitialized variables.
Check for circular dependencies in a dependency graph.
Performs cycle detection on a dependency graph structure using depth-first search. Uses three-color DFS (white=unvisited, gray=visiting, black=visited) to detect cycles efficiently.
Pike source code to analyze.
Optionalfilename:
string
Optional filename for the code.
Circular dependency check result with cycle path if found.
Check if the Pike executable is available.
true if Pike can be executed.
Clear batch parse metrics
PERF-003: Clear all tokenization caches. Call when clearing all document data.
Compile Pike code and get diagnostics.
Compiles the code using Pike's compiler and returns all errors and warnings. Useful for real-time validation.
Pike source code to compile.
Optionalfilename:
string
Optional filename for error messages.
Parse result with diagnostics from compilation.
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
Evaluate a constant Pike expression and return its value.
Compiles and evaluates a constant expression to get its runtime value. Used for inline values feature to display variable values in the editor.
The Pike expression to evaluate.
Optionalfilename:
string
Optional filename for error messages.
Evaluation result with value, type, and success status.
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) ]
Extract import/include/inherit/require directives from Pike code.
Parses Pike source code and extracts all module import directives, including preprocessor directives (#include, #require) and keyword statements (import, inherit).
Pike source code to parse.
Optionalfilename:
string
Optional filename for error reporting.
All imports found with their types and line numbers.
Find all identifier occurrences using Pike tokenization.
Uses Pike's native tokenizer to find exact positions of all identifiers in the code. More accurate than regex-based searching as it understands Pike's lexical grammar.
Pike source code to search.
All token occurrences with line and character positions.
Find all positions where a symbol can be renamed.
Uses Pike's Rename.pike module for accurate tokenization and position tracking.
Pike source code to analyze
The symbol name to find
Line number where the symbol is referenced (1-based)
Optionalcharacter:
number
Optional character position for precise matching (0-based)
Optionalfilename:
string
Optional filename for error reporting
Positions where the symbol occurs
Get batch parse metrics from recent operations
Get compilation cache statistics from the Pike subprocess.
Returns cache hit/miss ratios and size information, useful for debugging cache effectiveness and memory usage.
Cache statistics including hits, misses, evictions, and size.
Get completion context at a specific position using Pike's tokenizer. This replaces regex-based heuristics with Pike's accurate tokenization.
PERF-003: When documentUri and version are provided, caches tokenization results to avoid re-tokenizing the entire file on every completion.
Source code to analyze
Line number (1-based)
Character position (0-based)
OptionaldocumentUri:
string
Optional document URI for caching
OptionaldocumentVersion:
number
Optional LSP document version for cache invalidation
Completion context with type, object name, and prefix
Get diagnostic information for debugging.
Returns the current configuration and state of the bridge.
Diagnostic information including options, running state, and PID.
Get inherited members from a class.
Returns all members (methods, variables, constants) that a class inherits from its parent classes and implemented interfaces.
Fully qualified class name (e.g., "SSL.File").
Inherited members with their source classes.
Returns the current max listener value for the
EventEmitter which is either set by
emitter.setMaxListeners(n) or defaults to
EventEmitter.defaultMaxListeners.
Query Pike's runtime include and module paths.
Returns the current include and module paths from Pike's master(), useful for resolving #include directives and module imports.
Pike runtime paths with include_paths and module_paths arrays.
Get startup phase timing metrics from the Pike subprocess.
Returns detailed timing information about the analyzer startup process, useful for performance debugging and optimization.
Startup metrics with phase timings in milliseconds.
Get the Pike version.
Version string (e.g., "8.0") or null if Pike is not
available.
Get the Pike version via RPC.
Queries the running Pike subprocess for its version information. Returns structured version data including major, minor, build, and display values.
Version information object or null if the bridge is not running
or method is not available.
Get symbols with waterfall loading (transitive dependency resolution).
Performs transitive symbol loading by recursively resolving all dependencies of the specified file. Implements waterfall pattern where symbols from dependencies are loaded with depth tracking for proper prioritization (current file > direct imports > transitive).
Pike source code to analyze.
Optionalfilename:
string
Optional filename for resolution context.
OptionalmaxDepth:
number
Maximum depth for transitive resolution (default: 5).
All symbols with provenance tracking and merge precedence applied.
Perform a comprehensive health check.
Checks Pike availability, version, and analyzer script existence. Useful for diagnosing configuration issues.
Health check result with detailed diagnostics.
Invalidate compilation cache entries for testing or debugging.
Forces cache invalidation for a specific file path. Useful for testing cache behavior or forcing recompilation of a specific file.
File path to invalidate cache for.
Whether to invalidate transitive dependencies (default: false).
Confirmation status with the invalidated path.
PERF-003: Clear tokenization cache for a document. Call when document is modified or closed.
URI of the document to invalidate
Check if the bridge is running.
true if the subprocess is started and connected.
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.
The name of the event being listened for
Optionallistener:
Function
The event handler function
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] ]
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
The name of the event.
The callback function
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
The name of the event.
The callback function
Parse Pike source code and extract symbols.
Uses Pike's native parser to extract declarations without compilation.
Pike source code to parse.
Optionalfilename:
string
Optional filename for error messages.
Parse result containing symbols and diagnostics.
Parse preprocessor conditional blocks (#if/#else/#endif).
Extracts the structure of preprocessor directives, including:
This is used for conditional symbol extraction, where symbols inside different preprocessor branches are tagged with metadata indicating which condition they belong to.
Pike source code to parse.
Object with blocks array containing preprocessor structure.
Prepare rename - get the symbol range at the given position.
Used to validate that rename is allowed at position and get the range of the symbol to be renamed.
Pike source code
Line number (1-based)
Character position (0-based)
Optionalfilename:
string
Optional filename
Symbol range info or null if not renamable
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.
The name of the event.
The callback function
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.
server.prependOnceListener('connection', (stream) => {
console.log('Ah, we have our first user!');
});
Returns a reference to the EventEmitter, so that calls can be
chained.
The name of the event.
The callback 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');
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.
OptionaleventName:
string
|
symbol
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 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:
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.
Resolve an import/include/inherit/require directive to its file path.
Given an import directive type and target, attempts to resolve it to a file path. Resolution logic varies by import type:
Type of import (include, import, inherit, require).
Module/path name to resolve.
OptionalcurrentFile:
string
Optional current file path for relative resolution.
Resolved path with existence status and error info.
Resolve an #include path to an absolute file location.
Resolves #include directives to actual file system paths. Handles relative includes (e.g., "utils.pike") and system includes (e.g., <Stdio.h>).
Path from #include directive (with or without quotes/brackets).
OptionalcurrentFile:
string
Current file path for resolving relative includes.
Include resolve result with path and existence flag.
Resolve a module path to a file location.
Resolves Pike module import paths to actual file system paths. Handles both absolute module paths (e.g., "Stdio.File") and relative imports (e.g., ".MyModule").
Module path to resolve (e.g., "Crypto.SHA256" or ".SHA256").
OptionalcurrentFile:
string
Current file path for resolving relative modules.
Absolute file path if found, null otherwise.
Resolve a Pike standard library module.
Loads and introspects a module from Pike's standard library. Uses lazy on-demand loading to avoid unnecessary overhead.
Dot-separated module path (e.g., "Stdio.File").
Stdlib module information with symbols and inheritance.
Detect Roxen module information in Pike code.
Analyzes Pike source code to identify Roxen module patterns, including module type, variables, and RXML tags.
Source code to analyze
Optionalfilename:
string
Filename for the document (optional)
Roxen module information
Extract RXML strings from Pike multiline string literals.
Detects and extracts RXML content embedded in Pike code using #"..." and #'...' multiline string syntax.
Pike source code to analyze.
Optionalfilename:
string
Optional filename for error reporting.
Object containing array of detected RXML strings.
Generate a Roxen module skeleton.
Optionaloptions:
{
includeComments?:
boolean;
includeDefvar?:
boolean
}
Get lifecycle callback information from Roxen module code.
Detects presence of create(), start(), stop(), and status() callbacks.
Pike source code to analyze for lifecycle callbacks.
Optionalfilename:
string
Optional filename for error reporting.
Object containing lifecycle information with detected callbacks.
Get RXML tag catalog from running Roxen server.
Queries a running Roxen server for available RXML tags. Returns tag metadata including name, type, and attributes.
OptionalserverPid:
number
Optional Roxen server process ID. If not provided, attempts to detect running server.
Array of RXML tag definitions.
Parse RXML tag definitions from Roxen module code.
Extracts simpletag and container function definitions from the code.
Pike source code to parse for tag definitions.
Optionalfilename:
string
Optional filename for error reporting.
Object containing array of parsed tag definitions.
Parse defvar calls from Roxen module code.
Extracts module variable definitions from defvar() calls.
Pike source code to parse for variable definitions.
Optionalfilename:
string
Optional filename for error reporting.
Object containing array of parsed variable definitions.
Validate Roxen module API compliance.
Performs Roxen-specific validation including:
Pike source code to validate
Optional filename for error messages
OptionalmoduleInfo:
Record<string,
unknown>
Optional Roxen module info from parsing
Roxen validation result with diagnostics
Enable or disable debug mode in the analyzer.
When debug mode is disabled, the analyzer skips string formatting for debug messages, improving performance.
Whether to enable debug mode.
Confirmation with the new debug mode state.
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.
Tokenize Pike source code.
Returns the lexical tokens from Pike's tokenizer, useful for syntax highlighting and accurate symbol position finding.
Pike source code to tokenize.
Array of tokens with position information.
StaticaddExperimental
Listens once to the abort event on the provided
signal.
Listening to the abort event 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
stopImmediatePropagation does 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]();
}
}
Disposable that removes the abort listener.
Staticget
Returns a copy of the array of listeners for the event named
eventName.
For EventEmitters this behaves exactly the same as calling
.listeners on 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] ]
}
StaticgetReturns the currently set max amount of listeners.
For EventEmitters this behaves exactly the same as calling
.getMaxListeners on 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
}
Staticlistener
A class method that returns the number of listeners for the given
eventName registered 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
The emitter to query
The event name
Staticon
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());
Use the close option 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'
Optionaloptions:
StaticEventEmitterIteratorOptions
An AsyncIterator that iterates eventName events
emitted by the emitter
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());
Use the close option 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'
Optionaloptions:
StaticEventEmitterIteratorOptions
An AsyncIterator that iterates eventName events
emitted by the emitter
Staticonce
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:
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 boom
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!
Optionaloptions:
StaticEventEmitterOptions
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:
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 boom
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!
Optionaloptions:
StaticEventEmitterOptions
Staticsetimport { setMaxListeners, EventEmitter } from 'node:events';
const target = new EventTarget();
const emitter = new EventEmitter();
setMaxListeners(5, target, emitter);
Optionaln:
number
A non-negative number. The maximum number of listeners per
EventTarget event.
Zero or more {EventTarget} or {EventEmitter} instances. If none are
specified, n is set as the default max for all newly
created {EventTarget} and {EventEmitter} objects.
PikeBridge - Communication layer with Pike subprocess.
Manages a Pike subprocess that provides parsing, tokenization, and symbol extraction capabilities using Pike's native utilities. Uses JSON-RPC protocol over stdin/stdout for communication.
Example