CodeVetter · Repo Unpack · Extension points
puppeteer/puppeteer
The code provides explicit hooks for transports, download providers, selectors, command composition, and Angular schematics. Internal factories separate browser-specific launch and protocol behavior from shared public abstractions. These interfaces have concrete contracts and caveats rather than uniform support guarantees. API documentation and suite configuration are additional integration points for changes that introduce capabilities.
- BrowserProvider implementations supply supports, getDownloadUrl, getExecutablePath, and getName; methods may be asynchronous, and provider documentation assigns compatibility responsibility to implementers.
- InstallOptions.providers enters an ordered chain with conditional default fallback; custom executable layouts are persisted into Cache metadata.
- ConnectionTransport defines send/close/onmessage/onclose, and connect accepts a supplied transport directly instead of constructing a WebSocket transport.
- CustomQueryHandlerRegistry registers queryOne/queryAll functions under alphabetic names, creates QueryHandler adapters, and appends serialized registration scripts; unregister/clear remove injected scripts.
- getQueryHandlerAndSelector checks custom handlers before built-ins and parses P selectors before falling back to CSS; NodeLocator.create obtains the owning page's default timeout.
- BrowserLauncher subclasses implement executablePath, defaultArgs, computeLaunchArguments, and cleanUserDataDir; PuppeteerNode's #getLauncher is the Chrome/Firefox factory.
- CLI.run composes the shared yargs command table under an optional prefix; the puppeteer wrapper supplies a browsers prefix, configured cache, pinned builds, and disables cache-path override.
- Angular collection.json maps schematic names to factories and schemas, while getCommandForRunner is the runner-selection table; TestSuites.json similarly maps automation-suite parameters to environment variables.