puppeteer-core ignores all PUPPETEER_* env variables.
puppeteer-core doesn't automatically download Chromium when installed.To sum up, the only differences between puppeteer-core and puppeteer are: Through its programmatic interface and disregards all the PUPPETEER_* env variables. Being a library, puppeteer-core is fully driven puppeteer-core doesn't download Chromium when installed. Puppeteer-core is a library to help drive anything that supports DevTools protocol. Being an end-user product, puppeteer supports a bunch of convenient PUPPETEER_* env variables to tweak its behavior. When installed, it downloads a version ofĬhromium, which it then drives using puppeteer-core. Puppeteer is a product for browser automation. PUPPETEER_* env variables are not accounted for in puppeteer-core.Įvery release since v1.7.0 we publish two packages: Puppeteer is only guaranteed to work with the bundled Chromium, use at your own risk.
It works without any problems, however, with this option, you should get more efficient resource usage (CPU and RAM) that could lead to a faster execution time. On Apple M1 devices Puppeteer by default downloads the version for Intel's processor which runs via Rosetta.
If Puppeteer doesn't find them in the environment during the installation step, a lowercased variant of these variables will be used from the npm config. Puppeteer looks for certain environment variables to aid its operations. For a version of Puppeteer purely for connection, see puppeteer-core.
Today's computers can do 5 billion instructions per second.When you install Puppeteer, it downloads a recent version of Chromium (~170MB Mac, ~282MB Linux, ~280MB Win) that is guaranteed to work with the API (customizable through Environment Variables). The first electronic digital computer, ENIAC (1945), could do 5000 instructions The first electrical computer, Z3 (1941), could do 5 instructions per second.
To learn more, check out the browser's own manual for developer tools:
Using professional hardware, while other sites attract hobbyists using older computers.Īnyway, data collected from W3Schools' log-files over many years clearly shows the longīrowser's developer tools can be used to inspect, edit and debug HTML, CSS, and JavaScript of the curently-loaded page. Different sitesĪttract different audiences. W3Schools' statistics may not be relevant to your web site. "The pure and simple truth is rarely pure and never simple."