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

qunit-page

v1.1.2

Published

A QUnit extension that allows you to easily write clean UI tests.

Downloads

12

Readme

QUnit Page

A QUnit extension that allows you to easily write clean UI tests.

Build Status

Features

  • Avoid flaky tests - QUnit Page test structure induces you to think considering the user perspective. Your test is structured in wait for/do something because it helps you to avoid false negatives.

  • Write your test in javascript - The browser knows only one language: JavaScript. So, why should we write our test in another language? When we write UI test in another language, we are introducing unnecessary layers. This layer makes it extremely hard to debug false negatives.

  • Framework freedom - UI tests are created from the final user perspective. An user doesn't know how the app was made, so why an UI test should know?

  • Browser freedom - You need to run tests in your CI tool, probably using a headless browser, like PhantomJS. But sometimes things go wrong... and you want to be free to choose your favorite browser in order to debug it.

Do you want to contribute?

All submissions are welcome. To submit a change, fork this repo, commit your changes, and send us a pull request.