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

node_collector

v3.0.0

Published

master [![CircleCI](https://circleci.com/gh/Artear/node_collector/tree/master.svg?style=svg)](https://circleci.com/gh/Artear/node_collector/tree/master)

Readme

Node Collector

master CircleCI

Node Collector is a node module built to collect data from any source, and distribute it to different subscribers.

It's intended to scale across different servers, so you could for example spawn 1 Collectors, and 5 Subscribers in 6 different servers, and as long as they all have the same app_name/app_version, and are connected to the same redis, they will all be synchronized.

If you run 2 or more Collectors in the same app_name/app_version, they will automatically handle a master/slave logic.

When a Subscriber is started, it will automatically receive all previously sent data.

It uses redis to pub/sub operations and storage.

##Usage var collector = new Collector( redis_client, test_app_name, test_app_version, 500, function (saveFn) { saveFn(test_key, test_data); } );

    var subscriber = new Subscriber(
        redis_client,
        redis_client_sub,
        test_app_name,
        test_app_version,
        function (err, data) {
              console.log(data);
            }
        });

    subscriber.startListening();
    collector.startCollecting();
    
    

For more use cases, see the test file