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

mockeer

v0.0.4

Published

mocking puppeteer network calls

Downloads

1,488

Readme

About

Mockeer is a Puppeteer helper library to run chrome headless browser in isolation.

How it works

Mockeer works by overriding Puppeteer's Request event and providing mock responses.

Mockeer works in Record and Play mode. In record mode it intercepts browser requests and saves them as json fixtures. In play mode it just replay those saved responses.

Installation

$ npm install mockeer

Usage

const mockeer = require('mockeer');
const puppeteer = require('puppeteer');

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  await mockeer(browser);
  await page.goto('https://www.example.com');
  await page.close();
  await browser.close();
})();

Save above script as index.js

  • Record mode
> node index.js
  • Play mode
> CI=true node index.js

See more examples here

See full list of configs below

API

See API.md for full list of API calls

GlobalOptions

|Parameter|type|required|description|default| |---------|----|--------|-----------|-------| |page|object|no|If puppeteer page object passed, only mock responses for that page will be recorded|null| |fixturesDir|string|no|Path to generated fixture files|./__mockeer_fixture__| |fixtureName|string|no|Path to generated fixture name|chrome-http-mocks| |replaceImage|boolean|no|Replace images with template image|false| |allowImageRecourses|boolean|no|If enabled image resources will be fetched from origin and not intercepted in play mode|false| |svgTemplate|string|no|A SVG image template that will replace images in the page|A solid gray svg image. Source here|

Links

See examples for usages and CI integration with jest

Visit project Slack Chat for general Q/A around project

See CONTRIBUTING.md if you want to contribute.

Gist example with vanilla node