Puppeteer Adapter

Use @chaos-maker/puppeteer for headless Chromium suites that need a small adapter around Puppeteer pages.

API

import {
  injectChaos,
  removeChaos,
  getChaosLog,
  getChaosSeed,
  useChaos,
  injectSWChaos,
  removeSWChaos,
  getSWChaosLog,
} from '@chaos-maker/puppeteer';

Function	Purpose
`injectChaos(page, config)`	Registers config and UMD source with `evaluateOnNewDocument()`.
`removeChaos(page)`	Stops chaos and removes registered init scripts where Puppeteer exposes script IDs.
`getChaosLog(page)`	Returns `ChaosEvent[]`.
`getChaosSeed(page)`	Returns the active seed or `null`.
`useChaos(page, config)`	Injects chaos and returns an async teardown function.
`injectSWChaos(page, config, options?)`	Sends config to the active Service Worker after it controls the page.
`removeSWChaos(page, options?)`	Stops chaos inside the active Service Worker.
`getSWChaosLog(page)`	Returns Service Worker chaos events buffered on the page.

Timing

Call before page.goto() for network, WebSocket, SSE, and GraphQL chaos. Puppeteer v21+ headless Chromium is the supported mode for v0.4.0.

SSE chaos and GraphQL operation matching also use injectChaos() before navigation. For Service Worker chaos, navigate first, wait for navigator.serviceWorker.controller, then call injectSWChaos() before the user action that triggers SW fetches.

UI chaos requires the DOM to exist, so do not pass a ui config into the pre-navigation injectChaos() call — the auto-bootstrap would run before document.body is available. Instead:

Call injectChaos(page, { network, websocket }) (or injectChaos(page, {})) before page.goto() to load the UMD bundle and install network/WebSocket interceptors.
Navigate with page.goto().
Start UI chaos after navigation with page.evaluate((cfg) => (window as any).chaosUtils.start(cfg), uiConfig) — pass uiConfig as an explicit argument because the callback runs in the browser context.