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

testchamber

v2.0.4

Published

utilities for testing

Readme

testchamber

a set of utilities for testing

getting started

  • install, probably as a dev dependency: npm install testchamber --save-dev
  • where needed, import as such
    • just data:
      • const { data } = require("testchamber")
      • or
      • import { data } from "testchamber"
    • ui and data
      • const {data, ui} = require("testchamber")
      • or
      • import { data, ui } from "testchamber"
    • as different names:
      • const {data: datatools, ui: uitools} = require("testchamber")
      • or
      • import { data as datatools, ui as uitools } from "testchamber"
    • all as "testchamber":
      • const testchamber = require("testchamber")
      • or
      • import * as testchamber from "testchamber"
  • update as needed:
    • npm update testchamber
    • npm install testchamber --save-dev
    • ...and you may also need to blow away node_modules and npm install again

usage

best way to see actual usage is to checkout the test specs.

ui

this class contains useful static methods to use for UI browser testing with playwright. it mostly offers helper methods that deal with Page and ElementHandles when using page.$$() and friends.

data

this class contains useful static methods for dealing with data, such as random number and string generation.

exe

this class contains execution helpers such as sleep and retry loops

maintainence cheat sheet

running tests (manual)

  • run setup: npm run setup
  • run the tests: npm test
  • run the tests without coverage: npm run test-nocoverage

new version in github

  • ensure branch (master) has appropriate version in package.json
  • click 'Releases'
  • click 'Draft new release'
  • tag with the version number
  • release
  • verify npm publish action worked

npm publish (manual)

  • version bump in package.json
  • commit bump to master
  • login if needed: npm login
  • publish: npm publish