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

qunit-puppeteer-reporter

v2.0.4

Published

headless browser testing for QUnit test suites

Downloads

13

Readme

qunit-puppeteer-reporter

headless browser testing for QUnit test suites, using Puppeteer to report results via the command line

$ qunit-reporter http://localhost:8000/test/
loading test suite at http://localhost:8000/test/
✓ passed 18 / 18 (106 ms)

Note that this intentionally focuses only on reporting success/failure; for details and debugging you'll want to open the test suite in a regular browser.

Getting Started

$ npm install qunit-puppeteer-reporter
$ npm install -g puppeteer

Due to its size, the Puppeteer package is expected to be installed separately so it can be used across multiple projects.

$ npx qunit-reporter /path/to/tests.html

Both local file paths and URLs are supported.

(Note that npx is merely a shortcut for commands in node_modules/.bin - you might also define npm scripts to use npm start, for example.)

Contributing

  • ensure Node is installed
  • npm install downloads dependencies
  • npm test checks code for stylistic consistency

Alternatives