Loading content
Puppeteer is a Node.js library to control Chromium or Chrome via the DevTools Protocol. It enables headless and headful browser automation for end-to-end testing, scraping, and rendering. The API offers fine-grained control over page interactions, network and performance metrics, integrates with CI pipelines and supports distributed browser workflows.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Puppeteer is a Node.js library to control Chromium/Chrome via the DevTools Protocol for browser automation, testing, and rendering.
Puppeteer originated at Google as a Node.js library for programmatically controlling Chrome and Chromium through the DevTools Protocol, initially for automated tests and browser workflows.
A Node process launches a browser and uses CDP to address pages, contexts, and targets. Actions, network interception, and screenshots can be controlled asynchronously; browser and runtime versions affect test behavior.
CDP connects the client to browser targets.
Browser contexts isolate sessions.
Automation scripts observe network and page state.
Puppeteer suits end-to-end tests, crawling, and server-side rendering when Chromium control is required. Stability depends on resilient selectors, browser versions, and disciplined resource management.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.