Principle:Puppeteer Puppeteer Browser Binary Installation
| Knowledge Sources | |
|---|---|
| Domains | Browser_Management, Package_Management |
| Last Updated | 2026-02-11 23:00 GMT |
Overview
A process that downloads, extracts, and caches browser binary archives from vendor distribution servers.
Description
Browser Binary Installation handles the complete download-to-ready pipeline for browser executables. The process involves:
- Constructing the download URL from the browser type, platform, and build ID
- Downloading the archive with progress reporting
- Extracting the archive (ZIP, TAR.BZ2, TAR.XZ, DMG, or EXE depending on platform)
- Storing the extracted binary in a structured cache directory
- Returning the executable path for subsequent launching
The cache directory structure follows the pattern: cacheDir/browser-platform-buildId/
Usage
Use browser installation when setting up automation environments, in CI/CD pipelines, or when a specific browser version is required. The puppeteer package runs installation automatically as a postinstall hook, but the API is available for programmatic use.
Theoretical Basis
# Installation pipeline
1. Construct download URL from (browser, platform, buildId)
2. Check cache — if already installed, return cached path
3. Download archive to temporary location with progress callback
4. Extract archive to cache directory
5. Set executable permissions (Linux/macOS)
6. Return InstalledBrowser with executablePath
Related Pages
Implemented By
Page Connections
Double-click a node to navigate. Hold to expand connections.
Principle
Implementation
Heuristic
Environment