![require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages](https://cdn.sanity.io/images/cgdhsj6q/production/be8ab80c8efa5907bc341c6fefe9aa20d239d890-1600x1097.png?w=400&fit=max&auto=format)
Security News
require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
port_agent
Advanced tools
A RPC-like facility for making inter-thread function calls.
Port Agent provides a simple and intuitive interface that makes inter-thread function calls easy. Please see the Usage or Examples for instructions on how to use Port Agent in your application.
Error
from the other thread back to the caller.Agent.register
) persist until deregistered (i.e., Agent.deregister
) .An instance of an Agent
facilitates communication across threads. The Agent
can be used in order to register a function in one thread and call it from another thread. Calls may be made from the main thread to a worker thread, and conversely from a worker thread to the main thread.
Late binding registrants will be called with previously awaited invocations; thus preventing a race condition. This means that you may await a call to a function that has not yet been registered. Once the function is registered in the other thread it will be called and its return value or Error
will be marshalled back to the caller.
Please see the Examples for variations on the Agent
's usage.
Agent
class.<threads.MessagePort>
or <threads.Worker>
The message port.name <string>
The name of the registered function.
...args <Array<unknown>>
Arguments to be passed to the registered function.
Returns: <Promise<T>>
Errors:
Error
, the Error
will be marshalled back from the other thread to this thread and the Promise
will reject with the Error
as its failure reason.Error
will be marshalled back from the other thread to this thread and the Promise
will reject with the unhandled exception as its failure reason.Error
will be marshalled back from the other thread to this thread and the Promise
will reject with the exit code as its failure reason.name <string>
The name of the registered function.
fn <(...args: Array<any>) => any>
The registered function.
Returns: <void>
name <string>
The name of the registered function.
Returns: <void>
Agent
instance.import { Agent } from 'port_agent';
Agent
by passing a parentPort
or a Worker
instance to the Agent
constructor:In the main thread,
const worker = new Worker(fileURLToPath(import.meta.url));
const agent = new Agent(worker);
or, in a worker thread,
const agent = new Agent(worker_threads.parentPort);
Agent
instance.Agent.register
method:agent.register('hello_world', (value: string): string => `Hello, ${value} world!`);
Agent.call
method:const greeting = await agent.call<string>('hello_world', 'happy');
console.log(greeting); // Hello, happy world!
In this example you will:
Agent
in the main thread.Agent
to await a call to the hello_world
function.Agent
in the worker thread.Agent
in order to register a function named abend
that will throw an Error
when it is called.Agent
in order to register a function named hello_word
to handle calls to the hello_world
function.Agent
in order to register a function named add
that will return the sum of two operands.greeting
to the console.Agent
to await a call to the function named add
.result
to the console.Agent
to await a call to the function named abend
.Error
from (11) and log the stack trace to the console.examples/simple/index.js
import { Worker, isMainThread, parentPort } from 'node:worker_threads';
import { fileURLToPath } from 'node:url';
import { Agent } from 'port_agent';
if (isMainThread) { // This is the main thread.
void (async () => {
const worker = new Worker(fileURLToPath(import.meta.url)); // (1)
const agent = new Agent(worker); // (2)
try {
const greeting = await agent.call('hello_world', 'another'); // (3)
console.log(greeting); // (8)
const result = await agent.call('add', 1, 1); // (9)
console.log(result); // (10)
await agent.call('abend', "This Error is expected, indeed.") // (11)
}
catch (err) {
console.error(err); // (12)
}
finally {
worker.terminate(); // (13)
}
})();
}
else { // This is a worker thread.
if (parentPort) {
const agent = new Agent(parentPort); // (4)
agent.register('abend', (message) => { throw new Error(message); }); // (5)
agent.register('hello_world', (value) => `Hello, ${value} world!`); // (6)
agent.register('add', (a, b) => a + b); // (7)
}
}
The example will log to the console something similar to this:
Hello, another world!
2
Error: This Error is expected, indeed.
at file:///port_agent/examples/simple/index.js:29:54
at Agent.tryPost (/port_agent/examples/simple/node_modules/port_agent/dist/index.js:145:33)
at MessagePort.<anonymous> (/port_agent/examples/simple/node_modules/port_agent/dist/index.js:114:36)
at [nodejs.internal.kHybridDispatch] (node:internal/event_target:762:20)
at exports.emitMessage (node:internal/per_context/messageport:23:28)
Please see the Simple example for a working implementation.
Please see the Comprehensive example for a working implementation.
Port Agent supports one to one communication over a MessagePort
. BroadcastChannel
s are not presently supported.
Port Agent is strictly focused on efficient communication over MessagePort
s. Port Agent will not support communication over other communication channels e.g., Socket
s, IPC, etc.
[1.4.1] - 2025-01-14
FAQs
A RPC-like facility for making inter-thread function calls.
The npm package port_agent receives a total of 0 weekly downloads. As such, port_agent popularity was classified as not popular.
We found that port_agent demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.