Unix / Windows
Basic events, sync flow, raw buffers, and multi-client broadcast on one machine.
Browse local examples →Pick one small pattern
Examples
Open only the transport and behavior you need. These are the 14.x Node.js examples; native Rust examples have their own focused page.
Run these with Node.js.
The node-ipc JavaScript package is Node.js-only and does not run in web browsers, whether bundled or unbundled. These examples use native process and socket APIs; they are not browser examples.
By transport
TCP
Local or remote stream clients and servers with the standard event contract.
Browse TCP examples →TLS
Certificate configurations from local development through mutual authentication patterns.
Browse TLS examples →UDP
Independent UDP4 endpoints, request/reply addressing, broadcasts, and raw datagrams.
Browse UDP examples →Clustered local sockets
Multiple Node.js processes coordinating around a local socket ownership model.
Browse cluster examples →All examples
See the complete repository tree when you need to compare multiple patterns.
Browse the example directory →Native Rust
Use the matching TCP, UDP, Unix/Windows, TLS-boundary, cluster, and Node/Rust interoperability examples.
Open Rust examples →By message pattern
Basic request / reply
Start with one client event and one server response. It is the clearest place to add validation and authorization.
ipc.server.on('request', (data, socket) => {
ipc.server.emit(socket, 'response', handle(data));
});Multi-client broadcast
Fan one event out to known sockets. Do not broadcast secrets or tenant-specific data.
ipc.server.on('notice', data => {
ipc.server.broadcast('notice', data);
});Raw buffers
Skip event framing for binary protocols or interoperability with non-Node peers.
ipc.config.rawBuffer = true;
ipc.config.encoding = 'utf8';
ipc.server.on('data', (buffer, socket) => {});Synchronous queue
Queue new client sends until the current request receives data from the server.
ipc.config.sync = true;
ipc.of.worker.emit('job', payload);Before copying
- Replace demo ids, ports, and certificate paths.
- Keep network binds on loopback unless remote access is intentional.
- Select the parser profile before creating the endpoint.
- Add application payload validation, identity, authorization, rate limits, and shutdown handling.
- Run the focused test set for the chosen transport and inspect generated coverage.