you're building another end-user product or library atop of DevTools protocol.However, you should use puppeteer-core if: In most cases, you'll be fine using the puppeteer package. 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: Being a library, puppeteer-core is fully driven through its programmatic interface and disregards all the PUPPETEER_* env variables. 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 Chromium, which it then drives using puppeteer-core. Puppeteer is a product for browser automation. (Diagram source: link) puppeteer vs puppeteer-coreĮvery release since v1.7.0 we publish two packages: Worker has a single execution context and facilitates interacting with WebWorkers.A Frame might have additional execution contexts that are associated with extensions. Frame has at least one execution context - the default execution context - where the frame's JavaScript is executed.There might be other frames created by iframe or frame tags.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |