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

playwright-api-mock

v0.3.1

Published

An automated API response snapshot tool for Playwright. This plugin records API network requests during test runs and reuses them as mocks for fast, reliable, and deterministic tests.

Readme

Playwright API Mock

A Playwright plugin for seamlessly recording and mocking API responses, accelerating your testing workflow.

🚀 Features

  • Automatic API recording into snapshot files.
  • Instant response mocking from saved snapshots for faster tests.
  • Flexible request matching (wildcards & regular expressions).
  • Configurable logging (silent, error, info levels).
  • Easy integration with Playwright's fixture system.

📦 Installation

npm add -D playwright-api-mock

🛠️ Usage

✅ Automatically Record and Mock API Responses

Extend Playwright's page fixture to automatically record and mock API calls:

// fixtures.ts
import { test as base } from '@playwright/test';
import { ApiMockPlugin } from 'playwright-api-mock';

export const test = base.extend({
  page: async ({ page }, use) => {
    const apiMock = new ApiMockPlugin(page, {
      urlMatch: '**/api/**',
      apiSnapshotsPath: '__snapshots__/api.json',
      logLevel: 'info',
      mock: true,
    });
    await apiMock.record();
    await use(page);
  },
});

Then, simply use your extended fixture in tests:

import { test, expect } from './fixtures';

test('Fetch user data', async ({ page }) => {
  await page.goto('/users/123');
  const text = await page.locator('body').textContent();
  expect(text).toContain('User');
});

🔧 Create a Custom Fixture

Alternatively, create a standalone API mock fixture for flexible usage:

import { test as base } from '@playwright/test';
import { ApiMockPlugin } from 'playwright-api-mock';

export const test = base.extend({
  apiMock: async ({ page }, use) => {
    const plugin = new ApiMockPlugin(page);
    await use(plugin);
  },
});

Then use it explicitly in your tests:

import { test, expect } from './fixtures';

test.describe('User Page', () => {
  test.beforeEach(async ({ apiMock }) => {
    await apiMock.record({
      urlMatch: '**/api/user/**',
      apiSnapshotsPath: '__snapshots__/userApi.json',
      mock: true,
    });
  });

  test('Load user data', async ({ page }) => {
    await page.goto('/users/123');
    const text = await page.locator('body').textContent();
    expect(text).toContain('User');
  });
});

⚙️ Configuration

Customize your plugin by passing an options object:

Note: This plugin currently records and replays only JSON responses. Requests returning non-JSON content will pass through without being stored.

const apiMock = new ApiMockPlugin(page, {
  urlMatch: '**/api/**',
  apiSnapshotsPath: '__snapshots__/api.json',
  logLevel: 'info',
  mock: true,
  getStoredHeaders: (headers) => {
    // optionally filter or modify headers before storing
    return { 'content-type': headers['content-type'] };
  },
});

PluginConfig interface

| Option | Type | Default | Description | |--------------------|--------------------------------------|----------------------|--------------------------------------------------| | urlMatch | string \| RegExp | **/* | Request URLs to record/mock | | apiSnapshotsPath | string | api_snapshots.json | Path to store/load snapshot files | | logLevel | 'silent' \| 'error' \| 'info' | 'info' | Level of logging detail | | mock | boolean | true | Use stored snapshots instead of real responses | | getStoredHeaders | (headers) => headers \| undefined | undefined | Function to modify or filter headers before saving|


📖 API Methods

record(config?: Partial<PluginConfig>): Promise<void>

Starts intercepting and recording API responses. Optionally override configuration per test or fixture.

🤝 How to Contribute

  1. Fork and clone this repository.
  2. Install dependencies with bun install and build the project:
    bun run build
  3. Explore the example Playwright project under test/demo/:
    bun run demo:start # optional: run the backend server
    bun run demo:test
  4. Create feature branches for your changes and open a pull request.

📜 License

MIT License. See LICENSE for details.