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

@slaplacian/upsflux

v0.1.0

Published

Reads tsups JSON lines from stdin and writes them to InfluxDB 3 (samples and events in separate tables)

Readme

upsflux

Reads the JSON lines that tsups prints and writes them to InfluxDB 3. No dependencies; Node 20.12+.

tsups monitor --json | upsflux --env-file .env --tag ups=senoid15

| tsups line | Database | Table | |-------------------------|-------------------------------------------|--------------| | {"type":"sample",...} | INFLUX_DATABASE (infrastructure) | ups_status | | {"type":"event",...} | INFLUX_EVENTS_DATABASE (same as above) | ups_event | | tsups status --json | same as sample | ups_status |

Anything else (non-JSON, other objects) is ignored.

ups_status: tags host + --tags; float fields inputVoltage, inputFaultVoltage, outputVoltage, loadPercent, frequency, batteryVoltage, batteryNominal, batterySOC, temperature; string status; booleans utilityFail, batteryLow, bypass, upsFailed, standby, testInProgress, shutdownActive, beeperOn.

ups_event: tags code (UTILITY_FAIL, COMM_FAIL, ...), severity (info / success / warning / critical), bit, host; fields message, count=1i, and the readings at the time of the event (inputVoltage, outputVoltage, loadPercent, batteryVoltage, batterySOC).

Setup

npm install -g @slaplacian/tsups @slaplacian/upsflux
cp .env.example .env   # fill in URL, token, database

The token needs write access to the database(s). InfluxDB 3 Core creates a database on first write, so a typo in INFLUX_DATABASE silently creates a new one; check the name.

Behaviour

  • Samples are batched and sent every --flush-interval seconds (10); events are sent immediately.
  • If InfluxDB is unreachable or returns an error, points stay in memory (newest 50 000 per database) and are sent once it is back. Malformed lines (HTTP 400) are dropped and logged; InfluxDB 3 still stores the valid lines of the same batch.
  • On end of input, Ctrl+C or SIGTERM, buffered points are flushed first.
  • --dry-run prints the line protocol instead of sending; --tee echoes the input so you still see tsups output.

Uses /api/v3/write_lp with millisecond timestamps.

Development

npm test        # line protocol conversion and the writer against a fake server
npm link        # puts your working copy of `upsflux` on your PATH

License

MIT