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

playback-api

v0.2.0

Published

Mock integration test api for playing back sets of test data

Readme

Playback-Api

Purpose

To replay sets of test data for automated test evaluation of the final output of headless deamons, scripts, etc.. that POST to an external API with no testing/staging/sandbox environment.

  • Takes an xml based POST (and variants e.g. application/atom+xml) and saves it to an in-memory data store
  • POSTed data can be played back from the /test/:testId endpoint for evaluation; data is expected to be keyed to a given run of the test suite
    • (TODO: how to key data sets? app version, TeamCity build #, Environment Var, ???)

Usage

npm start spins up the server listening on the listenPort value in config

testId as a URL parameter in the routes refers to a given run of the acceptance test suite; all test data should be grouped together for any single run of the test suite

Routes:

  • /test/:testId POST/GET/DELETE data corresponding to a testId
    • POST: append data to this testId
    • GET: return list of data POSTed under this testId
    • DELETE: delete the list of data under this testId
  • /test/all DELETE all data in memory

TODO:

  • Cap the node-cache total size to something reasonable
  • Parse non-xml inputs