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

hemera-controlplane

v3.0.0

Published

This is a plugin to scale your workers remotly with Hemera

Downloads

13

Readme

Hemera-controlplane package

npm styled with prettier

This is a plugin to scale your workers remotly with Hemera. This package allows you to react dynamically to load requirements. Each worker has its own memory, with their own V8 instance. If you scale a worker inside a docker container ensure that you docker host has enough memory. The maximal number of workers is restricted to the processor count of the host machine.

Status: Experimental

  • Create easy multiple workers of your hemera service
  • When parent worker exit all child workers will exit
  • online and exit status are guaranteed via IPC
  • Receive further events e.g when a worker exists fast after it was successfully created

Run tests

$ node ./test/worker
$ npm run test

Start your worker

'use strict'

const Hemera = require('nats-hemera')
const nats = require('nats').connect()
const HemeraControlPlane = require('hemera-controlplane')
const HemeraJoi = require('hemera-joi')

const hemera = new Hemera(nats, {
  logLevel: 'debug'
})

hemera.use(HemeraJoi)
hemera.use(HemeraControlPlane, {
  service: 'math'
})

hemera.ready(() => {
  hemera.add({
    topic: 'math',
    cmd: 'add'
  }, (req, cb) => {
    cb(null, req.a + req.b)
  })
})

Scale your worker

'use strict'

const Hemera = require('nats-hemera')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'debug'
})

hemera.ready(() => {
  hemera.act({
    topic: 'controlplane',
    cmd: 'scaleUp',
    service: 'math',
    maxMessages$: 2 // receive further error events when the creation of the worker fails
  }, (err, req) => {
    hemera.log.info(req, 'Result') // {"success":true,"pid":5500}
  })
})

Scale your worker down

'use strict'

const Hemera = require('nats-hemera')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'debug'
})

hemera.ready(() => {
  hemera.act({
    topic: 'controlplane',
    cmd: 'scaleDown',
    service: 'math',
    maxMessages$: 2 // receive further error events when the killing of the worker fails
  }, (err, req) => {
    hemera.log.info(req, 'Result') // {"success":true,"pid":5500}
  })
})

Kill all workers but keep the parent process

'use strict'

const Hemera = require('nats-hemera')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'debug'
})

hemera.ready(() => {
  hemera.act({
    topic: 'controlplane',
    cmd: 'down',
    service: 'math'
  }, (err, req) => {
    hemera.log.info(req, 'Result') // {"success":true}
  })
})

Exit a worker by PID

'use strict'

const Hemera = require('nats-hemera')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'debug'
})

hemera.ready(() => {
  hemera.act({
    topic: 'controlplane',
    cmd: 'killByPid',
    service: 'math',
    pid: 1,
    maxMessages$: 2 // receive further error events when killing of the worker fails
  }, (err, req) => {
    hemera.log.info(req, 'Result') // {"success":true}
  })
})

Get list of all running workers

'use strict'

const Hemera = require('nats-hemera')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'debug'
})

hemera.ready(() => {
  hemera.act({
    topic: 'controlplane',
    cmd: 'list',
    service: 'math'
  }, (err, req) => {
    hemera.log.info(req, 'Result') // {"success":true, list: [5500]}
  })
})

TODO

  • [X] Use IPC to guarantee that process was started or exited.
  • [ ] Add more tests