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

url-content-changes-checker

v1.1.1

Published

A Node.js script to read and compare a remote resource body

Downloads

6

Readme

Build Status Build Cron Coverage Status

url-content-changes-checker

A Node.js script to read and compare a remote resource content.

What it does

This package:

  • reads a remote text-based resource
  • compares it with the previous one
  • if it changed saves the latest version...
  • ... logs the comparison... alt text
  • ... and saves a readable HTML file alt text

Example

const checker = require("url-content-changes-checker");

checker([
  {
    url: "http://example.com/schema",
    dir: "example-schema",
    fileNamePrefix: "schema"
  }
]);

produces the following file system

history
└───example-schema
│   │   schema-1550135407094
│   │   schema-1550136769927
│   │   schema-1550136769927.html
│   │   schema-1550136789201
│   │   schema-1550136789201.html

Options

checker(list, options)

  • list: an array of
    • url: the utl to be fetched
    • dir: the directory where the different versions of the content are stored
    • fileNamePrefix: the prefix for the version files (default: item)
    • resourceReader: a custom resource fetcher (Axios.get is used by default) that receives the url and must returns a Promise resolving with a {data} object
  • options
    • rootDir: the dir where every file is persisted (default: history)

If you want to dive more check the tests directory.

Why

I developed this script because I needed to check some text resources (GraphQL schemas, Elastic Search mappings, JSONs etc.) from some private (VPN protected) endpoints. A pipelined solution would be better but, at the time I wrote this script, I can't leverage my backend and devops colleagues.

Notes

  • The comparison is based on jsdiff.

Contributors

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!