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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@diginet/node-red-dygraphs

v0.0.2

Published

Graphs for node-red's dashboard UI using dygraphs

Downloads

2

Readme

node-red-dygraphs

Graphs for node-red's dashboard UI using dygraphs.

WARNING: this is a very rough prototype!

Nodes

Dygraph

The dygraph node is a would-be dashboard UI node to display a graph that is implemented as a standard node that pushes the right magic into a template node. In other words, the dygraph node is intended to always be coupled with a UI template node.

The dygraph node understands several input messages. The standard message to add a live data point contains:

  • msg.at: seconds since epoch, microsec since epoch, Date object, or null (for Date.now())
  • msg.payload: numerical value or NaN/null for missing value, or 3-value array with avg, min, max
  • msg.topic: name of series

(Not yet implemented:) In order to initialize the node with historical data a message with an array of data points can be piped in:

  • msg.payload: array of data points, each point being an object with ...

The various options of dygraphs can be controlled by passing an options field in:

  • msg.options: object with dygraph options (forwarded as-is, i.e., see dygraphs documentation)

Resample (not implemented)

The purpose of the resample node is to align the data points of multiple series in order to improve the on-hove display of values and to allow stacking. The assumption here is that various measurements come in at arbitrary times and the resample node aligns them at regular intervals using linear interpolation between sample points.

When there are multiple data points within one resampled interval the resample node can optionally produce min/max values resulting in a shaded range around the point in dygraphs.

Rate (not implemented)

The rate node converts a counter into a rate suitable to pipe to dygraphs. The input to the rate node is the same as that of the dygraph node except that it interprets values as monotonically increasing counters and converts the delta between two data points to a per-second rate, which it outputs.