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

streamr-monitor

v31.0.4-3

Published

This package parses PM2 log files and utilizes a Streamr broker node to send messages.

Readme

Summary

This package parses PM2 log files and utilizes a Streamr broker node to send messages.

Prerequisites

The host that is running your broker node(s) will need to utilize PM2 to manage the processes.

You'll need to know the name of each PM2 process you want to monitor. You can specify the names when starting your broker nodes.

If you wanted to start a broker node with a PM2 name of foo, you would use the following:

pm2 start --name foo streamr-broker -- /your/home/directory/.streamr/config/default.json

To review the state of PM2, you can run a status check:

pm2 status

If everything worked, you should see a table with your broker node running.

Install

npm install -g streamr-monitor

After the package has been installed, you'll need to edit to the .env file that was created, located at:

/your/home/directory/.streamr-monitor/config/.env

BROKER_NODE_URL=http://your-broker-node.com
BROKER_NODE_PORT=7101
BROKER_NODE_APKI_KEY=yourBrokerNodeApiAuthenticationKey

STREAM_ID=yourStreamId

PM2_LOG_DIRECTORY=/probably/your/home/directory/.pm2/logs
PM2_NAMES=foo,bar,hello,world

Check ENV

After you've updated the .env, you can confirm the environment variables are being found:

streamr-monitor env

Start

If everything looks good, you're now ready to start the monitor.

streamr-monitor start

You may even want to utilize PM2 to manage the monitor as well, in which case you'd start the monitor like this:

pm2 start --name monitor streamr-monitor