Skip to main content
Version: 2.3

utils.puppeteer

A namespace that contains various utilities for Puppeteer - the headless Chrome Node API.

Example usage:

const Apify = require('apify');
const { puppeteer } = Apify.utils;

// Open https://www.example.com in Puppeteer
const browser = await Apify.launchPuppeteer();
const page = await browser.newPage();
await page.goto('https://www.example.com');

// Inject jQuery into a page
await puppeteer.injectJQuery(page);

puppeteer.addInterceptRequestHandler

Adds request interception handler in similar to page.on('request', handler); but in addition to that supports multiple parallel handlers.

All the handlers are executed sequentially in the order as they were added. Each of the handlers must call one of request.continue(), request.abort() and request.respond(). In addition to that any of the handlers may modify the request object (method, postData, headers) by passing its overrides to request.continue(). If multiple handlers modify same property then the last one wins. Headers are merged separately so you can override only a value of specific header.

If one the handlers calls request.abort() or request.respond() then request is not propagated further to any of the remaining handlers.

Example usage:

// Replace images with placeholder.
await addInterceptRequestHandler(page, request => {
if (request.resourceType() === 'image') {
return request.respond({
statusCode: 200,
contentType: 'image/jpeg',
body: placeholderImageBuffer,
});
}
return request.continue();
});

// Abort all the scripts.
await addInterceptRequestHandler(page, request => {
if (request.resourceType() === 'script') return request.abort();
return request.continue();
});

// Change requests to post.
await addInterceptRequestHandler(page, request => {
return request.continue({
method: 'POST',
});
});

await page.goto('http://example.com');

Parameters:

Returns:

Promise<void>


puppeteer.removeInterceptRequestHandler

Removes request interception handler for given page.

Parameters:

Returns:

Promise<void>


puppeteer.gotoExtended

Extended version of Puppeteer's page.goto() allowing to perform requests with HTTP method other than GET, with custom headers and POST payload. URL, method, headers and payload are taken from request parameter that must be an instance of Apify.Request class.

NOTE: In recent versions of Puppeteer using requests other than GET, overriding headers and adding payloads disables browser cache which degrades performance.

Parameters:

Returns:

Promise<(Response|null)>


puppeteer.infiniteScroll

Scrolls to the bottom of a page, or until it times out. Loads dynamic content when it hits the bottom of a page, and then continues scrolling.

Parameters:

  • page: Page - Puppeteer Page object.
  • [options]: object
    • [timeoutSecs]: number = 0 - How many seconds to scroll for. If 0, will scroll until bottom of page.
    • [waitForSecs]: number = 4 - How many seconds to wait for no new content to load before exit.
    • [scrollDownAndUp]: boolean = false - If true, it will scroll up a bit after each scroll down. This is required on some websites for the scroll to work.
    • [buttonSelector]: string - Optionally checks and clicks a button if it appears while scrolling. This is required on some websites for the scroll to work.
    • [stopScrollCallback]: function - This function is called after every scroll and stops the scrolling process if it returns true. The function can be async.

Returns:

Promise<void>


puppeteer.saveSnapshot

Saves a full screenshot and HTML of the current page into a Key-Value store.

Parameters:

  • page: Page - Puppeteer Page object.
  • [options]: object
    • [key]: string = "SNAPSHOT" - Key under which the screenshot and HTML will be saved. .jpg will be appended for screenshot and .html for HTML.
    • [screenshotQuality]: number = 50 - The quality of the image, between 0-100. Higher quality images have bigger size and require more storage.
    • [saveScreenshot]: boolean = true - If true, it will save a full screenshot of the current page as a record with key appended by .jpg.
    • [saveHtml]: boolean = true - If true, it will save a full HTML of the current page as a record with key appended by .html.
    • [keyValueStoreName]: string | null = null - Name or id of the Key-Value store where snapshot is saved. By default it is saved to default Key-Value store.

Returns:

Promise<void>


puppeteer.enqueueLinksByClickingElements(options)

The function finds elements matching a specific CSS selector in a Puppeteer page, clicks all those elements using a mouse move and a left mouse button click and intercepts all the navigation requests that are subsequently produced by the page. The intercepted requests, including their methods, headers and payloads are then enqueued to a provided RequestQueue. This is useful to crawl JavaScript heavy pages where links are not available in href elements, but rather navigations are triggered in click handlers. If you're looking to find URLs in href attributes of the page, see utils.enqueueLinks().

Optionally, the function allows you to filter the target links' URLs using an array of PseudoUrl objects and override settings of the enqueued Request objects.

IMPORTANT: To be able to do this, this function uses various mutations on the page, such as changing the Z-index of elements being clicked and their visibility. Therefore, it is recommended to only use this function as the last operation in the page.

USING HEADFUL BROWSER: When using a headful browser, this function will only be able to click elements in the focused tab, effectively limiting concurrency to 1. In headless mode, full concurrency can be achieved.

PERFORMANCE: Clicking elements with a mouse and intercepting requests is not a low level operation that takes nanoseconds. It's not very CPU intensive, but it takes time. We strongly recommend limiting the scope of the clicking as much as possible by using a specific selector that targets only the elements that you assume or know will produce a navigation. You can certainly click everything by using the * selector, but be prepared to wait minutes to get results on a large and complex page.

Example usage

await Apify.utils.puppeteer.enqueueLinksByClickingElements({
page,
requestQueue,
selector: 'a.product-detail',
pseudoUrls: [
'https://www.example.com/handbags/[.*]'
'https://www.example.com/purses/[.*]'
],
});

Parameters:

  • options: object - All enqueueLinksByClickingElements() parameters are passed via an options object with the following keys:

    • page: Page - Puppeteer Page object.
    • requestQueue: RequestQueue - A request queue to which the URLs will be enqueued.
    • selector: string - A CSS selector matching elements to be clicked on. Unlike in utils.enqueueLinks(), there is no default value. This is to prevent suboptimal use of this function by using it too broadly.
    • [pseudoUrls]: Array<(string|RegExp|Object<string, *>)> - An array of PseudoUrls matching the URLs to be enqueued, or an array of strings or RegExps or plain Objects from which the PseudoUrls can be constructed.

    The plain objects must include at least the purl property, which holds the pseudo-URL string or RegExp. All remaining keys will be used as the requestTemplate argument of the PseudoUrl constructor, which lets you specify special properties for the enqueued Request objects.

    If pseudoUrls is an empty array, null or undefined, then the function enqueues all links found on the page.

    • [transformRequestFunction]: RequestTransform - Just before a new Request is constructed and enqueued to the RequestQueue, this function can be used to remove it or modify its contents such as userData, payload or, most importantly uniqueKey. This is useful when you need to enqueue multiple Requests to the queue that share the same URL, but differ in methods or payloads, or to dynamically update or create userData.

    For example: by adding useExtendedUniqueKey: true to the request object, uniqueKey will be computed from a combination of url, method and payload which enables crawling of websites that navigate using form submits (POST requests).

    Example:

    {
    transformRequestFunction: request => {
    request.userData.foo = 'bar';
    request.useExtendedUniqueKey = true;
    return request;
    };
    }
    • [waitForPageIdleSecs]: number = 1 - Clicking in the page triggers various asynchronous operations that lead to new URLs being shown by the browser. It could be a simple JavaScript redirect or opening of a new tab in the browser. These events often happen only some time after the actual click. Requests typically take milliseconds while new tabs open in hundreds of milliseconds.

    To be able to capture all those events, the enqueueLinksByClickingElements() function repeatedly waits for the waitForPageIdleSecs. By repeatedly we mean that whenever a relevant event is triggered, the timer is restarted. As long as new events keep coming, the function will not return, unless the below maxWaitForPageIdleSecs timeout is reached.

    You may want to reduce this for example when you're sure that your clicks do not open new tabs, or increase when you're not getting all the expected URLs.

    • [maxWaitForPageIdleSecs]: number = 5 - This is the maximum period for which the function will keep tracking events, even if more events keep coming. Its purpose is to prevent a deadlock in the page by periodic events, often unrelated to the clicking itself. See waitForPageIdleSecs above for an explanation.

Returns:

Promise<Array<QueueOperationInfo>> - Promise that resolves to an array of QueueOperationInfo objects.


puppeteer.injectFile(page, filePath, [options])

Injects a JavaScript file into a Puppeteer page. Unlike Puppeteer's addScriptTag function, this function works on pages with arbitrary Cross-Origin Resource Sharing (CORS) policies.

File contents are cached for up to 10 files to limit file system access.

Parameters:

  • page: Page - Puppeteer Page object.
  • filePath: string - File path
  • [options]: object
    • [surviveNavigations]: boolean - Enables the injected script to survive page navigations and reloads without need to be re-injected manually. This does not mean, however, that internal state will be preserved. Just that it will be automatically re-injected on each navigation before any other scripts get the chance to execute.

Returns:

Promise<*>


puppeteer.injectJQuery(page)

Injects the jQuery library into a Puppeteer page. jQuery is often useful for various web scraping and crawling tasks. For example, it can help extract text from HTML elements using CSS selectors.

Beware that the injected jQuery object will be set to the window.$ variable and thus it might cause conflicts with other libraries included by the page that use the same variable name (e.g. another version of jQuery). This can affect functionality of page's scripts.

The injected jQuery will survive page navigations and reloads.

Example usage:

await Apify.utils.puppeteer.injectJQuery(page);
const title = await page.evaluate(() => {
return $('head title').text();
});

Note that injectJQuery() does not affect the Puppeteer's page.$() function in any way.

Parameters:

  • page: Page - Puppeteer Page object.

Returns:

Promise<*>


puppeteer.injectUnderscore(page)

Injects the Underscore library into a Puppeteer page.

Beware that the injected Underscore object will be set to the window._ variable and thus it might cause conflicts with libraries included by the page that use the same variable name. This can affect functionality of page's scripts.

The injected Underscore will survive page navigations and reloads.

Example usage:

await Apify.utils.puppeteer.injectUnderscore(page);
const escapedHtml = await page.evaluate(() => {
return _.escape('<h1>Hello</h1>');
});

Parameters:

  • page: Page - Puppeteer Page object.

Returns:

Promise<*>


puppeteer.blockRequests(page, [options])

Forces the Puppeteer browser tab to block loading URLs that match a provided pattern. This is useful to speed up crawling of websites, since it reduces the amount of data that needs to be downloaded from the web, but it may break some websites or unexpectedly prevent loading of resources.

By default, the function will block all URLs including the following patterns:

[".css", ".jpg", ".jpeg", ".png", ".svg", ".gif", ".woff", ".pdf", ".zip"]

If you want to extend this list further, use the extraUrlPatterns option, which will keep blocking the default patterns, as well as add your custom ones. If you would like to block only specific patterns, use the urlPatterns option, which will override the defaults and block only URLs with your custom patterns.

This function does not use Puppeteer's request interception and therefore does not interfere with browser cache. It's also faster than blocking requests using interception, because the blocking happens directly in the browser without the round-trip to Node.js, but it does not provide the extra benefits of request interception.

The function will never block main document loads and their respective redirects.

Example usage

const Apify = require('apify');

const browser = await Apify.launchPuppeteer();
const page = await browser.newPage();

// Block all requests to URLs that include `adsbygoogle.js` and also all defaults.
await Apify.utils.puppeteer.blockRequests(page, {
extraUrlPatterns: ['adsbygoogle.js'],
});

await page.goto('https://cnn.com');

Parameters:

  • page: Page - Puppeteer Page object.
  • [options]: object
    • [urlPatterns]: Array<string> - The patterns of URLs to block from being loaded by the browser. Only * can be used as a wildcard. It is also automatically added to the beginning and end of the pattern. This limitation is enforced by the DevTools protocol. .png is the same as *.png*.
    • [extraUrlPatterns]: Array<string> - If you just want to append to the default blocked patterns, use this property.

Returns:

Promise<void>


puppeteer.cacheResponses(page, cache, responseUrlRules)

Deprecated

NOTE: In recent versions of Puppeteer using this function entirely disables browser cache which resolves in sub-optimal performance. Until this resolves, we suggest just relying on the in-browser cache unless absolutely necessary.

Enables caching of intercepted responses into a provided object. Automatically enables request interception in Puppeteer. IMPORTANT: Caching responses stores them to memory, so too loose rules could cause memory leaks for longer running crawlers. This issue should be resolved or atleast mitigated in future iterations of this feature.

Parameters:

  • page: Page - Puppeteer Page object.
  • cache: Object<string, *> - Object in which responses are stored
  • responseUrlRules: Array<(string|RegExp)> - List of rules that are used to check if the response should be cached. String rules are compared as page.url().includes(rule) while RegExp rules are evaluated as rule.test(page.url()).

Returns:

Promise<void>


puppeteer.compileScript(scriptString, context)

Compiles a Puppeteer script into an async function that may be executed at any time by providing it with the following object:

{
page: Page,
request: Request,
}

Where page is a Puppeteer Page and request is a Request.

The function is compiled by using the scriptString parameter as the function's body, so any limitations to function bodies apply. Return value of the compiled function is the return value of the function body = the scriptString parameter.

As a security measure, no globals such as process or require are accessible from within the function body. Note that the function does not provide a safe sandbox and even though globals are not easily accessible, malicious code may still execute in the main process via prototype manipulation. Therefore you should only use this function to execute sanitized or safe code.

Custom context may also be provided using the context parameter. To improve security, make sure to only pass the really necessary objects to the context. Preferably making secured copies beforehand.

Parameters:

  • scriptString: string
  • context: Object<string, *>

Returns:

CompiledScriptFunction