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

teenytest-e2e

v1.1.0

Published

Use puppeteer for browser e2e testing

Readme

teenytest-e2e

Use puppeteer for browser testing in teenytest.

Basics

In your teenytest helper, call teenytest-e2e's beforeAll from beforeAll, afterEach from afterEach and afterAll from afterAll.

  • beforeAll creates the browser and gives you a newPage() global
  • afterEach will close any pages you created with newPage()
  • afterAll closes the browser

If you want to take screenshots when tests fail, then also register teenytest-e2e as a teenytest plugin in your package.json. By default screenshots will be stored in a directory called screenshots. This can be configured by setting the environment variable SCREENSHOT_DIR.

global.newPage() creates a new wrapped page that has internals.methods wrapped and exposed. It only wraps a whitelist of methods to keep the API lean so other browsers can hopefully be supported in future.

Killer features

  • you don't have to create any browser pages but you can create as many as you want
  • each page has a promise that will reject the moment an unhandled JavaScript exception occurs
  • all supported page methods are wrapped with Promise.race with the above promise, so if an error occurs in the page the command will fail and rethrow that browser error
  • all console output in the page is output with your tests
  • page.waitForAny() waits for both good and bad selectors to appear in the page. Good ones resolve the promise, bad ones reject. Whichever comes first. So you can trigger an action and wait for the success state and any possible errors, then fail fast rather than time out because the success state never appeared.
  • page.pause() will similarly reject if an error occurs