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

webextension-rpc

v0.3.0

Published

Remote Procedure Call implementation for WebExtensions, to easily call functions across content scripts and background script.

Downloads

8

Readme

webextension-rpc

This module provides a Remote Procedure Call abstraction around the message passing that is available to WebExtension (browser extension) scripts. It makes it easier to call a function in the background script from a tab’s content script, or vice versa.

Example use

In background.js:

import { RpcServer } from 'webextension-rpc'
async function myFunc(arg) {
  return arg * 2
}
new RpcServer({ myFunc })

In content_script.js:

import { RpcClient } from 'webextension-rpc'
const myRemoteFunc = new RpcClient().func('myFunc')
await myRemoteFunc(21) // 42!

Note that the remote function always returns a Promise, which resolves with the remote function’s actual return value (if the return value is itself a Promise, its result is awaited too).

Use in TypeScript

When used TypeScript, the type of a remote/proxy function is nearly equal to its original, and can be derived from it automatically. For an example how to do this, see the example folder.

Install

Using NPM

This module is published on npm, as an ES module.

Run npm install webextension-rpc or equivalent, and in your code import what you need, e.g.:

import { RpcClient, RpcServer } from 'webextension-rpc'

API

RpcClient

new RpcClient(options?) (constructor)

Instantiate the RpcClient.

Arguments:

  • options (object, optional):
    • options.tabId (number): The id of the tab whose content script is the remote side. Leave undefined or null to invoke functions in the background script (from a content script).

func(functionName, options?)

Create a proxy function that invokes the specified remote function.

Arguments:

  • functionName (string, required): name of the function as registered on the remote side.
  • options (object, optional): override any options passed to the constructor.

RpcServer

new RpcServer(functions) (constructor)

Register one or more functions to enable remote scripts to call them.

Arguments:

  • functions (object, required): An object with a { functionName: function } mapping. Each function will be remotely callable using the given name.

injectRpcInfo

If the special symbol injectRpcInfo is passed as the first argument to a proxy function, this argument will be replaced on the executing side by an RpcInfo object, which contains the following attributes:

  • tab: the Tab, from which the call was made, if it was made by a content script.