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

node-fping

v0.0.2

Published

A simple wrapper for fping

Downloads

8

Readme

node-fping

A simple wrapper for fping

Requirements

Obviously, you need to have fping installed.

sudo apt-get install fping

Installation

npm install node-fping

Usage

Here is a usage example, with the results of just me hotspotted to my phone:

var fping = require('node-fping').subnet; // aliased to .network

fping('192.168.43.0/24', function(err, hosts) {
  // outputs: [  '192.168.43.1' , '192.168.43.63'  ]
  console.dir(hosts);
});

Caveats

Since I was the only use case for this, I did hardcode the arguments so that the code above will call /usr/bin/fping -r0 -aqg 192.168.43.0/24:

  • -r0 means it will only try to ping each host once
  • -a means only live hosts will be output to stdout
  • -q means stop printing dead hosts to stderr
  • -g means generate the hosts list from the given network

Also err will always be set as fping returns error code 1 unless every single host replies.

Todo

  • make it properly async, fping will output an IP address as soon as it gets a reply
  • allow pinging an array of hosts module.exports.hosts = function(hosts, callback) {}
  • allow specifying CLI options as an object