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

@lcoq/pinger

v0.0.2

Published

Read sitemap or file containing one URL per line, and ping its URLs

Downloads

6

Readme

@lcoq/pinger

A small script for pinging URLs from a sitemap or one-url-by-line file.

$ pinger /path/to/file
$ pinger http://domain.com/path/to/file
$ pinger /path/to/unzipped/sitemap.xml -s
$ pinger http://domain.com/sitemap.xml.gz -sg

Table of Contents

Requirements

pinger requires the following to run:

Usage

pinger is easiest to use when installed with npm.

Install it globally so you'll have access to the pinger command anywhere on your system.

$ npm install -g @lcoq/pinger

Then you can run pinger with the following command:

pinger <file-path-or-url>

pinger pings once each URLs in a file separated by a newline.

pinger <sitemap.xml.gz-path-or-url> -sg

pinger pings once each URLs in the given .xml.gz sitemap file.

Options

pinger supports the following options:

-s, --sitemap             Parse file as a .xml sitemap
-g, --gzip                Unzip .gz file
-t, --timeout <seconds>   Seconds before request timeout (default to 5)
-r, --repeat <count>      Number of times URLs are pinged (default to 1)
-b, --bunch <count>       Group requests by bunch of <count> requests and execute them simultaneously (default to 1)
-h, --help                output usage information
-V, --version             output the version number

Report

pinger reports for each URL pinged the status code of the response and the time elapsed during the request-response cycle (including redirects).

When pinger is used with the --timeout option, each URL that ended in a request timeout is also reported:

http://www.google.com 200 (0.36s)
http://www.google.fr 200 (0.38s)
http://www.bing.com TIMEOUT

pinger also provides a report once all URLs are pinged:

--- Report ---
Success: 792
Timeout: 4
Error: 0
---

Contributing

To contribute to pinger, please clone this repository locally, commit your code in a separate branch and open a pull-request.

License

pinger is licensed under the MIT license.

Copyright © 2016, Louis Coquio