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

cerebral-signals

v0.2.2

Published

signals implementation of Cerebral

Downloads

15

Readme

cerebral-signals

A mixed synchronous and asynchronous flow control tool

Creating a custom signal

const CerebralSignal = require('cerebral-signals')

const MySignal = CerebralSignal([
  // Context providers
])

const signal = MySignal([
  actionA,
  actionB
])

Included context providers

Input

Any payload passed into signal or updated using "next" will be available on the context as "input".

const CerebralSignal = require('cerebral-signals')
const InputProvider = require('cerebral-signals/providers/Input')

const MySignal = CerebralSignal([
  InputProvider()
])

function actionA(context) {
  context.input.foo // "bar"
}

const signal = MySignal([
  actionA
])

signal({
  foo: 'bar'
})

Output

Actions without any output will progress automatically. If you want to go down a specific path, pass payload and/or run async, you need an output to do that.

const CerebralSignal = require('cerebral-signals')
const OutputProvivder = require('cerebral-signals/providers/Output')

const MySignal = CerebralSignal([
  OutputProvivder()
])

function actionA(context) {
  // Trigger next action manually with a payload
  context.output({
    foo: 'bar'
  })
}

function actionB(context) {
  // If InputProvider was available the updated
  // (merged) payload would be available on "input"

  // Goes down to actionC, argument would be a payload.
  // This is run async, which is why the action is marked
  // as async as well
  setTimeout(() => context.output.alt1())
}
actionB.async = true

const signal = MySignal([
  actionA,
  actionB, {
    alt1: [],
    alt2: []
  }
])

signal()