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 🙏

© 2025 – Pkg Stats / Ryan Hefner

handy-ms-broker-nats

v0.0.5

Published

`handy-ms-broker-nats` registers all `async` function of a class and then be callable by the other microservice.

Downloads

1

Readme

handy-ms-broker-nats

handy-ms-broker-nats registers all async function of a class and then be callable by the other microservice.

How it works?

Lets say you have a SampleController class from one of your microservice, and you want it to be callable on the other node.js microservice.

// sample_ctl.js

class SampleController {
  async foo (params) {
    return Promise.resolve({ action: 'foo', params })
  }

  async bar (params) {
    return Promise.resolve({ action: 'bar', params })
  }

  async sampleerr () {
    return Promise.reject(new Error('Sample Err'))
  }
}

All you have to do is connect to your NATS, pass it to handy-ms-broker-nats instance, then register your SampleController

// ms-app-1/index.js (aka subscriber)

const NATS = require('nats')
const Broker = require('handy-ms-broker-nats')

const nats = NATS.connect()
const broker = new Broker(nats)

broker.register('resource', new SampleController())

Then, it is now callable by the other end.

// ms-app-2/index.js (aka publisher)

const NATS = require('nats')
const Broker = require('handy-ms-broker-nats')

const nats = NATS.connect()
const broker = new Broker(nats)

broker.call('resource.foo', { hey: 'ho!' })
  .then(ret => {
    console.log(ret) // { action: 'foo', params: { hey: 'ho!' } }
  })
  .catch(err => {
    if (/Sample Err$/.test(err.message)) {
      // catching our defined err
    } else {
      throw err // if isn't ours
    }
  })

In Constructor Registration

class Foo {
  constructor (broker) {
    this.broker = broker

    this.broker.register('myService', this)
  }

  async foo (params) {
    return Promise.resolve({ action: 'foo', params })
  }

  async sampleCall (params) {
    return this.broker.call('otherService', params)
  }
}

const NATS = require('nats')
const Broker = require('handy-ms-broker-nats')

const nats = NATS.connect()
const broker = new Broker(nats)

const foo = new Foo(broker)

foo.sampleCall(params)
  .then(ret => console.log(ret))
  .catch(err => console.log(err))