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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@modulae.systems/rpc-client

v1.0.3

Published

An RPC client module

Readme

Introduction

This is a simple RPC Client that allows easier implementation of RPC. This might be too simplified and could be difficult to customise to your exact needs, but do try it. Hope it helps simplify your development effort! Cheers~

Notice

@modulae.systems/rpc-client is best used with

Upgrade Note:

v1.x.x is not compatible with v0.x.x. There is a breaking changes, removing callFunction() method, and replaced with callPublicMethod() and callProtectedMethod(). Updated this module to feel more like calling methods, as per the intention of RPC itself.

Install

npm i @modulae.systems/rpc-client

Usage

Public RPC calls (without requiring Tokens)

import { callPublicMethod } from "@modulae.systems/rpc-client";

function login() {
    let loginData = {
        user: "blablabla",
        pass: "34819d7beeabb9260a5c854bc85b3e44",
    }
    const loginResponse = await callPublicMethod(process.env.RPC_URL,"login",loginData);
    if (!loginResponse.error) {
        const responseData = loginResponse.data;
        // process the data here
    } else {
        // display your error with loginResponse.error.description
        // or handle the error according to the code returned with loginResponse.error.code
        // you may also debug with loginResponse.error.debug if your rpc-server is returning any error debug objects defined by your team
    }
}

Protected RPC calls (require Tokens)

import { callProtectedMethod } from "@modulae.systems/rpc-client";

function editProfile(token: string) {
    let changedProfile = {
        name: "blablabla",
    }
    const profileResponse = await callProtectedMethod(process.env.RPC_URL,"editProfile",changedProfile,token);
    if (!profileResponse.error) {
        const responseData = profileResponse.data;
        // process the data here
    } else {
        // display your error with profileResponse.error.description
        // or handle the error according to the code returned with profileResponse.error.code
        // you may also debug with profileResponse.error.debug if your rpc-server is returning any error debug objects defined by your team
    }
}

For your .env file

RPC_URL=http://mywebsite.com # enter the url to your rpc server, likely localhost during development

For apps with React, you need to use the REACT_APP_ prefix, making the key as REACT_APP_RPC_URL=xxxx instead of just RPC_URL=xxxx For apps with VueJS, you need to use the VUE_APP_ prefix, making the key as VUE_APP_RPC_URL=xxxx instead of just RPC_URL=xxxx