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

happner-suite

v4.3.0

Published

happner-suite (WIP) ------------------- This is a work in progress and is not for public consumption yet. We have moved all separate happner components together into a monorepo, for ease of development.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jeggersjeggers

Keywords

Readme

happner-suite (WIP)

This is a work in progress and is not for public consumption yet. We have moved all separate happner components together into a monorepo, for ease of development.

We are also modernizing a lot of the internals, and will be re-doing the documentation - which has admittedly prevented adoption by anyone who has not worked on this framework.

The happner suite has 4 top-level modules:

  1. happn-3 - the bottom layer, this manages data-storage, pub/sub and security. happn-3 can be used independently from the other layers - it's technical equivalent would be firebase.
  2. happner-2 - the rpc layer, this sits on top of happn-3 and provides a means of exposing javascript module methods to the outside world.
  3. happn-cluster - sits on top of happn-3, allows for the creation of a pub/sub cluster.
  4. happner-cluster - sits on top of happn-3, happner-2 and happn-cluster, allows for the creation of a clustered rpc setup, where work is distributed across multiple cluster nodes in the cloud.

major releases (migration documentation)

setup:

git clone https://github.com/happner/happner-suite.git
cd happner-suite
npm i

main modules:

happn-3 coverage

This the pub/sub and datastorage layer of the system - happn-3 is similar to firebase in a lot of respects, it combines datastorage with an events communicated over websockets.

happner-2 coverage

This is the rpc layer, it uses happn-3 for communication, and provides the ability to discover and call server-side components as if they were local.

happn-cluster coverage

Adds cluster capability to happn-3.

happner-cluster coverage

Adds cluster-capability to happner-cluster.

supporting modules:

data providers:

The data providers are plugins that need to be setup as npm dependencies and configured as data providers

happn-db-provider-loki coverage

the default embedded data provider, see loki

// configure in happn

// configure in happner

happn-db-provider-mongo coverage

mandatory for clustered setup or situations where there is high data volume

// configure in happn

// configure in happner

happn-db-provider-nedb

still maintained for backward compatability - this was the original default embedded data provider (will eventually be discontinued)

// configure in happn

// configure in happner