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 🙏

© 2026 – Pkg Stats / Ryan Hefner

hypertest

v0.2.1

Published

test a hyper+json API

Readme

hypertest

test a hyper+json api interface

Installation

$ npm install -g hypertest

Usage

$ hypertest path/to/test.spec.yml

  ....

  4 passing (2s)

hypertest(1) accepts the same flags as mocha

See format for details.

Format

hypertest expects a yaml document describing the tests. A document includes the host name, optional headers and a set of paths with one or more assertions.

The most basic assertion is a simple string. The available methods are described by should.js

host: http://api.example.com

.account.name: should exist

With (optional) headers

host: http://api.example.com
headers:
  header1: value1
  header2: value2
  
.account.name: should exist

Additionally, reference to environment variables is possible

host: $HOST
headers:
  authorization: $AUTH_TOKEN

Since should exist is so common it is the default assertion.

host: http://api.example.com

.account.name:

Assertions can also be a list of assertion statements.

.account.name:
  - should eql 'Frank'
  - should startWith 'F'
  - should endWith 'nk'
  - should be type 'string'
  - should be a String

If more complex assertions are needed inline javascript functions are available.

.account.name:
  - !!js/function >
    function(value, done) {
      // complex testing here
      done();
    }

The function can also be given a human-readable name.

.account.name:
  -
    name: should do some really complex thing
    fn: !!js/function >
      function(value, done) {
        // complex testing here
        done();
      }

The values for the custom functions get injected in by reading the names of the arguments specified. A list of default values includes:

val, value

The value of the body at the end of the path

res

The response object returned by superagent

path, key

The path used in the test

should

should.js module used for testing

hyperagent, hyper

hyperagent context used to make the request

require

CommonJS require function to require any other needed modules

done, cb, fn

Function to be called when the assertions are done executing. This is required for any async assertions.