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

cdnwhaaat

v1.2.1

Published

Check that your files are on the CDN.

Downloads

14

Readme

CDN...Whaat!

This script simply helps you checking that some files have been uploaded to your CDN.

cdnwhaat

It is usually common to build some assets (optimized images, minified JS) on your server and then send them to your CDN -- but better check they have really been uploaded, else your deployment will reserve you some nasty surprises!

Installation

Install this module globally

npm install -g cdnwhaaat

Usage

cdnwhaaat /path/to/your/assets --cdn=https://cdn.example.org/assets/ [--tries 5] [--sleep 3]

The first argument is the path to your assets on the machine where cdnwhaaat is running: it will recursively iterate through the contents of that path and extract the files that need to be checked on the --cdn argument.

In the example above, say there is a sample.txt file in /path/to/your/assets, then cdnwhaaat will try to hit it at https://cdn.example.org/assets/sample.txt.

The --tries argument specifies how many times cdnwhaat should try to hit that file until it should consider it failed (a hit is considered successful when it returns 200 Ok).

The --sleep argument will instead specify how many seconds we will wait before the next attempt: in the example above we try 5 times, with 3 seconds between each try.

~/projects/namshi/cdnwhaaat  ᐅ cdnwhaaat /tmp/cdn --cdn=https://a.namshicdn.com/ --tries 3 --sleep 1
Attempting to verify everything is on the CDN (1)
Attempting to verify everything is on the CDN (2)
Attempting to verify everything is on the CDN (3)
Some resources weren't found on the CDN
https://a.namshicdn.com/phoenix/styles/some.html

Tests

tests

For real, still trying to figure how to do them.