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

@chimps/js-rpc

v0.0.11

Published

rpc over nats.

Downloads

35

Readme

rpc-js

The whole plan is to make it easy to do rpc. The base concept is to send and hanlde messages (over nats).

Handler

This replaces both workers and events and combines them both into one simple context. Handlers get registered to a path with an optional group, to make them share the load of that queue.

Messages still looks like this:

{
    metadata:{<bunch of headers>},
    body:<up to you>
}

An example

This example will echo what ever got sent to the topic echo.

const {nats, model} = require('../')

// connect to nats
const c = nats.Server.connect()

// bind a handler to the echo queue, expecting to be called with request.
c.handler('echo', null, ctx => {
    let m = ctx.body()
    
    ctx.reply(m)
})

c.start("test")

To consume the above rpc service:

const {nats, model} = require('../')

// connect to nats
const c = nats.Server.connect()

// request a response from echo, give it 3000 millis to respond to us.
let res = await c.request('echo', model.Message.newEmptyStringBody(), 3000)
// res will now contain a model.Message response.