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

smokedetector

v1.0.5

Published

a simple smoke test utility for websites

Downloads

4

Readme

smokedetector

A simple smoke test utility for websites.

Philosophy

Smokedetector is intended to automate the most basic checks for a website. (In QA terms: It runs a smoke test.)

Smokedetector can be used to automatically check if:

  • Your homepage works
  • Your robots.txt and sitemap.xml are accessible
  • Your landing pages are available
  • Your redirect from http:// to https:// works
  • any important URL is working

Preliminary configuration is kept to an absolute minimum. You have to provide

  • your hostname (e.g. www.google.com)
  • the URLs you want smoketest to check (e.g. "/", "/robots.txt", "/very/important/landingpage.html")

Usage

To start using smokedetector in a project, run:

npx smokedetector --init

Optional: add more URLs to the file smokedetector.json.

Whenever you want to make sure that your site is working, run:

npx smokedetector

The first time this is run, smokedetector assumes a known-good system, i.e. the responses of the system are recorded and subsequent runs of smokedetector expect the same responses to occur.

What does it do?

smokedetector reads host and path information from the file smokedetector.json. It constructs URLs and makes a request. If smokedetector has not visited the URL, the HTTP status code and (in case of redirects) the "Location"-Header is recorded. From now on, every run of smokedetector expects the same response code and "Location"-header (if applicable). If the response codes do not match the expectation, smokedetector tells you.

The smokedetector.json file

This is an example of the configuration file:

{
  "description": "This configuration is used by smokedetector. smokedetector allows you to quickly check that the most important urls on a website work. Learn more at https://github.com/digital-sailors/smokedetector",
  "servers": {
    "live": {
      "host": "www.digital-sailors.de"
    }
  },
  "urlspace": {
    "http": {
      "/": {},
      "/your/other/http/urls/here.html": {}
    },
    "https": {
      "/": {},
      "/your/other/https/urls/here.html": {}
    }
  }
}

It is created when you run npx smokedetector --init. You can add any number of URLs, ones that should work with https:// and ones that work with http://

When you run smokedetector, it records the responses in this file. The file is considered diff-aware, i.e. changes happen when something significant changed. If you find this file modified without reason, that probably means that a smoke test gave a different result than the one that was expected.

Multiple Hosts

TBA

HTTP downgrade

TBA

Advanced use cases

Compare a staging system and the live system

Handle non-HTTPS systems

License

Licensed under

Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)

Contribution Licensing

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be licensed as above, without any additional terms or conditions.