npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-ipc-call

v0.0.5

Published

Non-blocking cross-process method call based on IPC for Node.js

Downloads

4

Readme

node-ipc-call

version downloads license Travis Coverage

Non-blocking cross-process method call based on IPC for Node.js.

$ npm install --save node-ipc-call

Usage

const { Caller } = require('node-ipc-call');

const invoker = Caller.fork('./foo.js');

await invoker.invoke('sleep', 1000);
await invoker.invoke('max', [1, 2, 3]); // 3

invoker.destroy();
// ./foo.js
const { Callee } = require('node-ipc-call');

const callee = new Callee();

// async method
callee.register(async function sleep(ms) {
  return new Promise((resolve) => {
    setTimeout(resolve, ms);
  });
});

// sync method
callee.register(function max(...args) {
  return Math.max(...args);
});

callee.listen();

API

Class: Caller

Added in: v0.0.1

Caller.fork(modulePath, args, options)

Added in: v0.0.1

Returns .

Class: Invoker

Added in: v0.0.1

Returned by Caller.fork(), you should make remote function calls via Invoker.

invoker.invoke(name, args[, options])

Added in: v0.0.1

  • name {String} The remote function name.
  • args {Array} Arguments passed to the remote function.
  • options {Object}
    • timeout {Number} In milliseconds. Default: 3000.

Returns <Promise>.

invoker.destroy()

Added in: v0.0.1

Closes the IPC channel to child process, and rejects all pending calls.

Class: Callee

Added in: v0.0.1

callee.register(arg)

Added in: v0.0.1

  • arg {Function|Object|Array} The functions or an array of functions exposed to remote call.

Each function to be registered should have an unique name, register the same function multiple times is ok.

callee.register(function foo() {});
callee.register({ foo() {} });
callee.register([ foo, bar ]);
callee.register(() => {}); // Error

callee.listen()

Added in: v0.0.1

Starts to listen for method calls from parent process.

callee.destroy()

Added in: v0.0.1

Stops listening method calls from parent process.

License

MIT