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

monitor-hafas-cli

v3.0.0

Published

Monitor any HAFAS endpoint from the command line.

Downloads

13

Readme

monitor-hafas-cli

Monitor any HAFAS endpoint from the command line.

npm version ISC-licensed minimum Node.js version support me via GitHub Sponsors chat with me on Twitter

Installation

npm install -g monitor-hafas-cli

Or use npx. ✨

Getting started

As an example, we're going to monitor the VBB HAFAS endpoint, using vbb-hafas@7.

# make an empty project to play around
mkdir vbb-monitoring
cd vbb-monitoring
npm init --yes

# set up HAFAS client
npm install vbb-hafas@7
echo 'const createHafas = require("vbb-hafas")' >>hafas.js
echo 'const hafas = createHafas("vbb monitoring example")' >>hafas.js
changes, 2.0.0
echo 'module.exports = hafas' >>hafas.js

# set up monitoring
events='departure'
stations='900000100001,900000100003'

# run monitor-hafas-cli using npx
npx monitor-hafas-cli@2 ./hafas.js $events stations $stations
# or install & run monitor-hafas-cli manually
npm install monitor-hafas-cli@2
./node_modules/.bin/monitor-hafas ./hafas.js $events stations $stations

Use record-hafas-data to store to record this data into a LevelDB.

Note: If you want to monitor by bounding box (bbox mode), you need a running Redis server.

Usage

Monitoring stations:
	monitor-hafas <hafas-client> <list of events> stations <list of stations>
	monitor-hafas <hafas-client> <list of events> stations --file <file with stations>
	available events: departure, stopover, stats
Monitoring trips in a bounding box:
	monitor-hafas <hafas-client> <list of events> bbox <north> <west> <south> <east>
	available events: trip, new-trip, trip-obsolete, stopover, position, stats
Options:
	--file          -f  Read the list of stations from a JSON file.
	--pretty-print  -f  Pretty print data instead of JSON.
	--interval      -i  Query interval in seconds. Default: 30
	--show-stats    -s  Always show request stats.
Examples:
	monitor-hafas vbb-hafas departure stations 900000100001,900000100003
	monitor-hafas ./my-hafas-client.js departure,stopover stations --file stations.json
	monitor-hafas some-package/my-hafas-client.js stopover,position bbox 52.6 13.3 52.3 13.6

Related

Contributing

If you have a question or need support using monitor-hafas-cli, please double-check your code and setup first. If you think you have found a bug or want to propose a feature, refer to the issues page.