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

jpc-core

v0.3.0

Published

Allows remote procedure calls between JS objects over event-like channels or the network

Downloads

14

Readme

jpc - Remote procedure calls between JS objects in different processes

jpc allows you to call JS objects in other processes. From your JS objects, it automatically creates an API that resembles your object API, just with an await in front of every call. It then transmits the call over the channel and call the objects in the remote process, and returns the result back to you.

It can work over various communication channels to communicate with the remote process:

API

Start object

This is what your client calls initially and gets the first object references from.

Objects

The remote API is the same as the local API, just with an await prepended to all calls, aside from new and setters.

| | Local object | Remote object | Difference | |----------|---------------------|---------------------------|--------------------------------------------------| | function | car.startEngine() | await car.startEngine() | same, just with await | | getter | car.owner | await car.owner | same, just with await | | setter | car.owner = val | await car.setOwner(val) | because setters always return the assigned value | | new | new Car() | await Car.newRemote() | because new always returns the object |

Example

Given an object of class

class Movable {
  constructor() {}
}
class Car extends Movable {
  constructor() {
    this.super();
    this._owner = "Fred Flintstone";
  }
  startEngine() {
    console.log("Engine started");
  }
  get owner {
    return this._owner;
  }
  set owner(val) {
    this._owner = val;
  }
}

The local API in the server process is standard JS:

let car = new Car();
car.owner = "Wilma";
console.log(car.owner);
car.startEngine();

The client API in the other process is almost the same, just with an await added in front of all calls:

let car = await Car.newRemote(); // creates a new object in the server process
await car.setOwner("Wilma");
console.log(await car.owner); // shows "Wilma" on the client
await car.startEngine(); // shows "Engine started" on the server