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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@ianwalter/puppeteer-helper

v4.0.0

Published

An AVA helper that makes a Puppeteer page available to a test

Readme

@ianwalter/puppeteer-helper

An AVA helper that makes a Puppeteer page available to a test

npm page

About

This helper is based on a recipe that can be found in AVA's docs.

Installation

yarn add @ianwalter/puppeteer-helper --dev

Warning

This is meant for testing. You wouldn't want to run untrusted code as root with this since sandboxing is disabled.

Usage

JavaScript to evaluate in the browser (something.js):

import subpub from '@ianwalter/subpub'

// Run your evaluation inside of `window.run` which passes the resolve/reject
// functions from the returned promise and an arg if a second argument is passed
// to `t.evaluate`.
window.run((resolve, reject, args) => {
  // Subscribe to the 'alerts' topic and resolve the evaluation when a message
  // is received.
  subpub.sub('alerts', data => resolve(data.msg))

  // Send a test message to the 'alerts' topic.
  subpub.pub('alerts', { msg: 'Winter Snow Advisory!' })
})

Using the evaluation script in an AVA test:

import test from 'ava'
import puppeteerHelper from '@ianwalter/puppeteer-helper'

const withPage = puppeteerHelper() // You can pass Puppeteer options here.

test('message received', withPage, async (t, page) => {
  t.is(await t.evaluate('./something.js'), 'Winter Snow Advisory!')
})

API

t.evaluate(evaluationScriptPath, [frame]) - Runs the evaluation script (path is relative to process.cwd()) on the given frame (defaults to page). Arguments to the evaluate call can be supplied by adding them to t.context.args. A custom Webpack config can also be added to t.context.webpack.

Debugging

To aid in debugging tests, pass { devtools: true } to the puppeteerHelper call and then add debugger to the problem area in your evaluation script. This will stop the browser from automatically running in headless mode and pause execution where debugger is placed. This is helpful if you, for example, want to see/modify a snapshot of variables in the execution context within Chrome DevTools.

Related

  • ianwalter/puppeteer - A GitHub Action / Docker image for Puppeteer, the Headless Chrome Node API

License

Apache 2.0 with Commons Clause - See LICENSE

 

Created by Ian Walter