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

electron-simple-rpc

v1.0.7

Published

It is a real PITA to call functions running in another electron thread/process.

Downloads

6

Readme

Electron Simple RPC (Remote Procedure Call)

Why?

It is a real PITA to call functions running in another electron thread/process.

This system lets you not only easily call a function running in a different thread but also get a response. Ultimatley, this is a fancy promise wrapper for electron's built-in IPC system. It works the same in any type of electron thread.

Install

npm install electron-simple-rpc

Usage

The RPC system needs to be setup in every electron thread you which to communicate between. A typical example would be.

Main Electron Thread:

  import { RpcIpcManger } from 'rpc';
  
  // Specify the scope (this should be unique)
  const scope = 'electron';
  
  // Create the function lib
  const library = {
    ping = (inputs) => {
      console.log('ping ' + inputs)
      return 'pong from electron'
    }
  }
  
  const rpcIpcManager = new RpcIpcManger(library, scope);
    

Renderer Thread:

  import { RpcIpcManger, rpc } from 'rpc';
  
  // Specify the scope (this should be unique)
  const scope = 'renderer1';
  
  // Create the function lib
  const library = {}
  
  const rpcIpcManager = new RpcIpcManger(library, scope);
  
  // We send an RPC event from renderer -> electron
  rpc('electron', 'ping')('from renderer').then(console.log)
  

Result:

Electron logs out: ping from renderer

Renderer logs outs: pong from electron

Note: This example shows renderer -> electron comms. The code is pretty much identical for renderer -> renderer or electron -> renderer. All you need to do is change the scope.


Functions

RPC Emit

rpc(scope, functionPathInLib)(functionInputs);

This will emit a Remote Procedure Call action (which will travel to all threads). This will run a function if scope is correct.

@param string scope             - The destination threads scope (electron, main-renderer etc)
@param string functionPathInLib - The path to the function in the destination thread's lib
@param any functionInputs       - The function inputs (must be serialisable, i.e. object, string, number etc)

RPC Manager

RpcIpcManger(lib, scope);

This is used to receive and respond to RPC actions received over IPC.

@param object lib   - The function library used with rpc
@param string scope - This thread's scope (electron, main-renderer etc)