- BrowserLaunchContext<PuppeteerPlugin[launchOptions], unknown>
useIncognitoPages, but for persistent contexts, so cache is used for faster loading.
Works best with Firefox. Unstable on Chromium.
Already required module (
Object). This enables usage of various Puppeteer
wrappers such as
Take caution, because it can cause all kinds of unexpected errors and weird behavior.
Crawlee is not tested with any other library besides
URL to a HTTP proxy server. It must define the port number, and it may also contain proxy username and password.
executablePath is not set,
Puppeteer will launch full Google Chrome browser available on the machine
rather than the bundled Chromium. The path to Chrome executable
is taken from the
CRAWLEE_CHROME_EXECUTABLE_PATH environment variable if provided,
or defaults to the typical Google Chrome executable location specific for the operating system.
By default, this option is
With this option selected, all pages will be opened in a new incognito browser context. This means they will not share cookies nor cache and their resources will not be throttled by one another.
User-Agent HTTP header used by the browser.
If not provided, the function sets
User-Agent to a reasonable default
to reduce the chance of detection of the crawler.
Sets the User Data Directory path. The user data directory contains profile data such as history, bookmarks, and cookies, as well as other per-installation local state. If not specified, a temporary directory is used instead.
Apify extends the launch options of Puppeteer. You can use any of the Puppeteer compatible
LaunchOptionsoptions by providing the