Crawlee—A web scraping and browser automation library for Node.js to build reliable crawlers. In JavaScript and TypeScript. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with Puppeteer, Playwright, Cheerio, JSDOM, and raw HTTP. Both headful and headless mode. With proxy rotation.
TypeScript apifyautomationcrawlercrawlingheadlessheadless-chromejavascriptnodejsnpmplaywrightpuppeteerscraperscrapingtypescriptweb-crawlerweb-crawlingweb-scraping
chore: build new version of docs
Ondra Urbandc9b3ca123f6
diff --git a/website/versioned_docs/version-1.1.0/api/Session.md b/website/versioned_docs/version-1.1.0/api/Session.mdnew file mode 100644index 000000000..8bc86b3b9--- /dev/null+++ b/website/versioned_docs/version-1.1.0/api/Session.md@@ -0,0 +1,207 @@+---+id: version-1.1.0-session+title: Session+original_id: session+---++<a name="session"></a>++Sessions are used to store information such as cookies and can be used for generating fingerprints and proxy sessions. You can imagine each session as+a specific user, with its own cookies, IP (via proxy) and potentially a unique browser fingerprint. Session internal state can be enriched with custom+user data for example some authorization tokens and specific headers in general.++---++<a name="exports.session"></a>++## `new Session(options)`++Session configuration.++**Parameters**:++- **`options`**: [`SessionOptions`](../typedefs/session-options)++---++<a name="userdata"></a>++## `session.userData`++---++<a name="isblocked"></a>++## `session.isBlocked()`++indicates whether the session is blocked. Session is blocked once it reaches the `maxErrorScore`.++**Returns**:++`boolean`++---++<a name="isexpired"></a>++## `session.isExpired()`++Indicates whether the session is expired. Session expiration is determined by the `maxAgeSecs`. Once the session is older than+`createdAt + maxAgeSecs` the session is considered expired.++**Returns**:++`boolean`++---++<a name="ismaxusagecountreached"></a>++## `session.isMaxUsageCountReached()`++Indicates whether the session is used maximum number of times. Session maximum usage count can be changed by `maxUsageCount` parameter.++**Returns**:++`boolean`++---++<a name="isusable"></a>++## `session.isUsable()`++Indicates whether the session can be used for next requests. Session is usable when it is not expired, not blocked and the maximum usage count has not+be reached.++**Returns**:++`boolean`++---++<a name="markgood"></a>++## `session.markGood()`++This method should be called after a successful session usage. It increases `usageCount` and potentially lowers the `errorScore` by the+`errorScoreDecrement`.++---++<a name="getstate"></a>++## `session.getState()`++Gets session state for persistence in KeyValueStore.++**Returns**:++[`SessionState`](../typedefs/session-state) - represents session internal state.++---++<a name="retire"></a>++## `session.retire()`++Marks session as blocked and emits event on the `SessionPool` This method should be used if the session usage was unsuccessful and you are sure that+it is because of the session configuration and not any external matters. For example when server returns 403 status code. If the session does not work+due to some external factors as server error such as 5XX you probably want to use `markBad` method.++---++<a name="markbad"></a>++## `session.markBad()`++Increases usage and error count. Should be used when the session has been used unsuccessfully. For example because of timeouts.++---++<a name="retireonblockedstatuscodes"></a>++## `session.retireOnBlockedStatusCodes(statusCode, [blockedStatusCodes])`++With certain status codes: `401`, `403` or `429` we can be certain that the target website is blocking us. This function helps to do this conveniently+by retiring the session when such code is received. Optionally the default status codes can be extended in the second parameter.++**Parameters**:++- **`statusCode`**: `number` - HTTP status code+- **`[blockedStatusCodes]`**: `Array<number>` - Custom HTTP status codes that means blocking on particular website.++**Returns**:++`boolean` - whether the session was retired.++---++<a name="setcookiesfromresponse"></a>++## `session.setCookiesFromResponse(response)`++Saves cookies from an HTTP response to be used with the session. It expects an object with a `headers` property that's either an `Object` (typical+Node.js responses) or a `Function` (Puppeteer Response).++It then parses and saves the cookies from the `set-cookie` header, if available.++**Parameters**:++- **`response`**: `PuppeteerResponse` | `IncomingMessage`++---++<a name="setpuppeteercookies"></a>++## `session.setPuppeteerCookies(cookies, url)`++Saves an array with cookie objects to be used with the session. The objects should be in the format that+[Puppeteer uses](https://pptr.dev/#?product=Puppeteer&version=v2.0.0&show=api-pagecookiesurls), but you can also use this function to set cookies+manually:++```+[+ { name: 'cookie1', value: 'my-cookie' },+ { name: 'cookie2', value: 'your-cookie' }+]+```++**Parameters**:++- **`cookies`**: `Array<PuppeteerCookie>`+- **`url`**: `string`++---++<a name="getpuppeteercookies"></a>++## `session.getPuppeteerCookies(url)`++Returns cookies in a format compatible with puppeteer and ready to be used with `page.setCookie`.++**Parameters**:++- **`url`**: `string` - website url. Only cookies stored for this url will be returned++**Returns**:++`Array<PuppeteerCookie>`++---++<a name="getcookiestring"></a>++## `session.getCookieString(url)`++Returns cookies saved with the session in the typical key1=value1; key2=value2 format, ready to be used in a cookie header or elsewhere.++**Parameters**:++- **`url`**: `string`++**Returns**:++`string` - represents `Cookie` header.++---diff --git a/website/versioned_docs/version-1.1.0/api/SessionPool.md b/website/versioned_docs/version-1.1.0/api/SessionPool.mdnew file mode 100644index 000000000..d66a8226f--- /dev/null+++ b/website/versioned_docs/version-1.1.0/api/SessionPool.md@@ -0,0 +1,164 @@+---+id: version-1.1.0-session-pool+title: SessionPool+original_id: session-pool+---++<a name="sessionpool"></a>++Handles the rotation, creation and persistence of user-like sessions. Creates a pool of [`Session`](../api/session) instances, that are randomly+rotated. When some session is marked as blocked, it is removed and new one is created instead (the pool never returns an unusable session). Learn more+in the [`Session management guide`](../guides/session-management).++You can create one by calling the [`Apify.openSessionPool`](../api/apify#opensessionpool) function.++Session pool is already integrated into crawlers, and it can significantly improve your scraper performance with just 2 lines of code.++**Example usage:**++```javascript+const crawler = new Apify.CheerioCrawler({+ useSessionPool: true,+ persistCookiesPerSession: true,+ // ...+});+```++You can configure the pool with many options. See the [`SessionPoolOptions`](../typedefs/session-pool-options). Session pool is by default persisted+in default [`KeyValueStore`](../api/key-value-store). If you want to have one pool for all runs you have to specify+[`SessionPoolOptions.persistStateKeyValueStoreId`](../typedefs/session-pool-options#persiststatekeyvaluestoreid).++**Advanced usage:**++```javascript+const sessionPool = await Apify.openSessionPool({+ maxPoolSize: 25,+ sessionOptions: {+ maxAgeSecs: 10,+ maxUsageCount: 150, // for example when you know that the site blocks after 150 requests.+ },+ persistStateKeyValueStoreId: 'my-key-value-store-for-sessions',+ persistStateKey: 'my-session-pool',+});++// Get random session from the pool+const session1 = await sessionPool.getSession();+const session2 = await sessionPool.getSession();+const session3 = await sessionPool.getSession();++// Now you can mark the session either failed or successful++// Marks session as bad after unsuccessful usage -> it increases error count (soft retire)+session1.markBad();++// Marks as successful.+session2.markGood();++// Retires session -> session is removed from the pool+session3.retire();+```++---++<a name="sessions"></a>++## `sessionPool.sessions`++---++<a name="usablesessionscount"></a>++## `sessionPool.usableSessionsCount`++Gets count of usable sessions in the pool.++**Returns**:++`number`++---++<a name="retiredsessionscount"></a>++## `sessionPool.retiredSessionsCount`++Gets count of retired sessions in the pool.++**Returns**:++`number`++---++<a name="initialize"></a>++## `sessionPool.initialize()`++Starts periodic state persistence and potentially loads SessionPool state from [`KeyValueStore`](../api/key-value-store). It is called automatically+by the [`Apify.openSessionPool`](../api/apify#opensessionpool) function.++**Returns**:++`Promise<void>`++---++<a name="addsession"></a>++## `sessionPool.addSession([options])`++Adds a new session to the session pool. The pool automatically creates sessions up to the maximum size of the pool, but this allows you to add more+sessions once the max pool size is reached. This also allows you to add session with overridden session options (e.g. with specific session id).++**Parameters**:++- **`[options]`**: [`Session`](../api/session) | [`SessionOptions`](../typedefs/session-options) - The configuration options for the session being+ added to the session pool.++---++<a name="getsession"></a>++## `sessionPool.getSession([sessionId])`++Gets session. If there is space for new session, it creates and returns new session. If the session pool is full, it picks a session from the pool, If+the picked session is usable it is returned, otherwise it creates and returns a new one.++**Parameters**:++- **`[sessionId]`**: `String` - If provided, it returns the usable session with this id, `undefined` otherwise.++**Returns**:++[`Promise<Session>`](../api/session)++---++<a name="getstate"></a>++## `sessionPool.getState()`++Returns an object representing the internal state of the `SessionPool` instance. Note that the object's fields can change in future releases.++---++<a name="persiststate"></a>++## `sessionPool.persistState()`++Persists the current state of the `SessionPool` into the default [`KeyValueStore`](../api/key-value-store). The state is persisted automatically in+regular intervals.++**Returns**:++`Promise<void>`++---++<a name="teardown"></a>++## `sessionPool.teardown()`++Removes listener from `persistState` event. This function should be called after you are done with using the `SessionPool` instance.++---diff --git a/website/versioned_docs/version-1.1.0/guides/getting_started.md b/website/versioned_docs/version-1.1.0/guides/getting_started.mdnew file mode 100644index 000000000..9ab957b40--- /dev/null+++ b/website/versioned_docs/version-1.1.0/guides/getting_started.md@@ -0,0 +1,1741 @@+---+id: version-1.1.0-getting-started+title: Getting Started+original_id: getting-started+---++Without the right tools, crawling and scraping the web can be a difficult thing. At the very least, you need an HTTP client to make the necessary+requests, but that only gets you raw HTML and sometimes not even that. Then you have to read this HTML and extract the data you're interested in. Once+extracted, it must be stored in a machine readable format and easily accessible for further processing, because it is the processed data that hold+value.++Apify SDK covers the process end-to-end. From crawling the web for links and scraping the raw data to storing it in various machine readable formats,+ready for processing. With this guide in hand, you should have your own data extraction solutions up and running in a few hours.++## Intro++The goal of this getting started guide is to provide a step-by-step introduction to all the features of the Apify SDK. It will walk you through+creating the simplest of crawlers that only prints text to console, all the way up to complex systems that crawl pages, interact with them as if a real+user were sitting in front of a real browser and output structured data.++Since Apify SDK is usable both locally on any computer and on the [Apify Platform](../guides/apify-platform), you will be able+to use the source code in both environments interchangeably. Nevertheless, some initial setup is still required, so choose your preferred starting+environment and let's get into it.++## Setting up locally++To run Apify SDK on your own computer, you need to meet the following pre-requisites first:++1. Have Node.js version 10.17 or higher, with the exception of Node.js 11, installed.+ - Visit [Node.js website](https://nodejs.org/en/download/) to download or use+ [nvm](https://github.com/creationix/nvm)+2. Have NPM installed.+ - NPM comes bundled with Node.js so you should already have it. If not, reinstall Node.js.++If you're not certain, confirm the pre-requisites by running:++```bash+node -v+```++```bash+npm -v+```++### Creating a new project++The fastest and best way to create new projects with the Apify SDK is to use our own+[Apify CLI](https://www.npmjs.com/package/apify-cli). This command line tool allows you to create, run and manage Apify+projects with ease, including their deployment to the [Apify platform](../guides/apify-platform) if you wish to run them in the+cloud after developing them locally.++Let's install the Apify CLI with the following command:++```bash+npm install -g apify-cli+```++Once the installation finishes, all you need to do to set up an Apify SDK project is to run:++```bash+apify create my-new-project+```++A prompt will be shown, asking to choose a template. Disregard the different options for now and choose the template labeled `Hello world`. The+command will now create a new directory in your current working directory, called `my-new-project`, create a `package.json` in this folder and install+all the necessary dependencies. It will also add example source code that you can immediately run.++Let's try that!++```bash+cd my-new-project+```++```bash+apify run -p+```++> The `-p` flag is great to remember, because it stands for `--purge` and it clears out your persistent storages before starting the actor.+> `INPUT.json` and named storages are kept. Whenever you're just restarting your actor and you're not interested in the data of the previous run, you+> should use `apify run -p` to prevent the old state from messing with your current run. If this is confusing, don't worry. You'll learn about+> storages and `INPUT.json` soon.++You should start seeing log messages in the terminal as the system boots up and after a second, a Chromium browser window should pop up. In the+window, you'll see quickly changing pages and back in the terminal, you should see the titles (contents of the `<title>` HTML tags) of the pages+printed.++You can always terminate the crawl with a keypress in the terminal:++```bash+CTRL+C+```++Did you see all that? If you did, congratulations! You're ready to go!++## Setting up on the Apify Platform++Maybe you don't have Node.js installed and don't want the hassle. Or you can't install anything on your computer because you're using a company+provided one. Or perhaps you'd just prefer to start working in the cloud right away. Well, no worries, we've got you covered.++The [Apify platform](../guides/apify-platform) is the foundational product of+[Apify](https://apify.com). It's a serverless cloud computing platform, specifically designed for any web automation jobs,+that may include crawling and scraping, but really works amazing for any batch jobs and long running tasks.++It comes with a free account, so let's go to our [sign-up page](https://my.apify.com/sign-up) and create one, if you+haven't already. Don't forget to verify your email. Without it, you won't be able to run any projects.++Once you're in, you might be prompted by our in-app help to walk through a step-by-step guide into some of our new features. Feel free to finish that,+if you'd like, but once you're done, click on the **Actors** tab in the left menu. To read more about **Actors**, see:+[What is an Actor](../guides/apify-platform#what-is-an-actor).++### Creating a new project++In the page that shows after clicking on Actors in the left menu, choose **Create new**. Give it a name in the form that opens, let's say,+`my-new-actor`. Disregard all the available options for now and save your changes.++Now click on the **Sources** tab at the top. Disregard the version and environment variables inputs for now and proceed directly to **Source code**.+This is where you develop the actor, if you choose not to do it locally. Just press **Run** below the **Source code** panel. It will automatically+build and run the example source code. You should start seeing log messages that represent the build and after the build is complete, log messages of+the running actor. Feel free to check out the other **Run** tabs, such as **Info**, where you can find useful information about the run, or+**Key-value-store**, where the actor's **INPUT** and **OUTPUT** are stored.++Good job. You're now ready to run your own source code on the Apify Platform. For more information visit the+[Actor documentation page](https://docs.apify.com/actor), where you'll find everything about the platform's various+options.++## First crawler++Whether you've chosen to develop locally or in the cloud, it's time to start writing some actual source code. But before we do, let me just briefly+introduce all the Apify SDK classes necessary to make it happen.++### The general idea++There are 3 crawler classes available for use in the Apify SDK. [`BasicCrawler`](../api/basic-crawler), [`CheerioCrawler`](../api/cheerio-crawler)+and [`PuppeteerCrawler`](../api/puppeteer-crawler). We'll talk about their differences later. Now, let's talk about what they have in common.++All the crawlers' general idea is to go to a web page, open it, do some stuff there, save some results and continue to the next page, until it's done+its job. So each time the crawler needs to find answers to two questions: **Where should I go?** and **What should I do there?**. Answering those two+questions is the only setup mandatory to run the crawlers.++### The Where - `Request`, `RequestList` and `RequestQueue`++All crawlers use instances of the [`Request`](../api/request) class to determine where they need to go. Each request may hold a lot of information,+but at the very least, it must hold a URL - a web page to open. But having only one URL would not make sense for crawling. We need to either have a+pre-existing list of our own URLs that we wish to visit, perhaps a thousand, or a million, or we need to build this list dynamically as we crawl,+adding more and more URLs to the list as we progress.++A representation of the pre-existing list is an instance of the [`RequestList`](../api/request-list) class. It is a static, immutable list of URLs and+other metadata (see the [`Request`](../api/request) object) that the crawler will visit, one by one, retrying whenever an error occurs, until there+are no more `Requests` to process.++[`RequestQueue`](../api/request-queue) on the other hand, represents a dynamic queue of `Requests`. One that can be updated at runtime by adding more+pages - `Requests` to process. This allows the crawler to open one page, extract interesting URLs, such as links to other pages on the same domain,+add them to the queue (called _enqueuing_) and repeat this process to build a queue of tens of thousands or more URLs while knowing only a single one+at the beginning.++`RequestList` and `RequestQueue` are essential for the crawler's operation. There is no other way to supply `Requests` = "pages to crawl" to the+crawlers. At least one of them always needs to be provided while setting up. You can also use both at the same time, if you wish.++### The What - `handlePageFunction`++The `handlePageFunction` is the brain of the crawler. It tells it what to do at each and every page it visits. Generally it handles extraction of data+from the page, processing the data, saving it, calling APIs, doing calculations and whatever else you need it to do, really.++The `handlePageFunction` is provided by you, the user, and invoked automatically by the crawler for each `Request` from either the `RequestList` or+`RequestQueue`. It always receives a single argument and that is a plain `Object`. Its properties change depending on the used crawler class, but it+always includes at least the `request` property, which represents the currently crawled `Request` instance (i.e. the URL the crawler is visiting and+related metadata) and the `autoscaledPool` property, which is an instance of the [`AutoscaledPool`](../api/autoscaled-pool) class and we'll talk about+it in detail later.++```js+// The object received as a single argument by the handlePageFunction+{+ request: Request,+ autoscaledPool: AutoscaledPool+}+```++### Putting it all together++Enough theory! Let's put some of those hard learned facts into practice. We learned above that we need `Requests` and a `handlePageFunction` to setup+a crawler. We will also use the [`Apify.main()`](../api/apify#main) function. It's not mandatory, but it makes our life easier. We'll+learn about it in detail later on.++Let's start super easy. Visit one page, get its title and close. First of all we need to require Apify, to make all of its features available to us:++```js+const Apify = require('apify');+```++Easy right? It doesn't get much more difficult, trust me. For the purposes of this tutorial, we'll be scraping our own webpage+[https://apify.com](https://apify.com). Now, to get there, we need a `Request` with the page's URL in one of our sources,+`RequestList` or `RequestQueue`. Let's go with `RequestQueue` for now.++```js+const Apify = require('apify');++// This is how you use the Apify.main() function.+Apify.main(async () => {+ // First we create the request queue instance.+ const requestQueue = await Apify.openRequestQueue();+ // And then we add a request to it.+ await requestQueue.addRequest({ url: 'https://apify.com' });+});+```++> If you're not familiar with the `async` and `await` keywords used in the example, trust that it is a native syntax in modern JavaScript and you can+> [learn more about it here](https://nikgrozev.com/2017/10/01/async-await/).++The [`requestQueue.addRequest()`](../api/request-queue#addrequest) function automatically converts the plain object we passed to it to a+`Request` instance, so now we have a `requestQueue` that holds one `request` which points to `https://apify.com`. Now we need the+`handlePageFunction`.++```js+// We'll define the function separately so it's more obvious.+const handlePageFunction = async ({ request, $ }) => {+ // This should look familiar if you ever worked with jQuery.+ // We're just getting the text content of the <title> HTML element.+ const title = $('title').text();++ console.log(`The title of "${request.url}" is: ${title}.`);+};+```++Wait, where did the `$` come from? Remember what we learned about the `handlePageFunction` earlier. It expects a plain `Object` as an argument that+will always have a `request` property, but it will also have other properties, depending on the chosen crawler class. Well, `$` is a property provided+by the `CheerioCrawler` class which we'll set up right now.++```js+const Apify = require('apify');++Apify.main(async () => {+ const requestQueue = await Apify.openRequestQueue();+ await requestQueue.addRequest({ url: 'https://apify.com' });++ const handlePageFunction = async ({ request, $ }) => {+ const title = $('title').text();++ console.log(`The title of "${request.url}" is: ${title}.`);+ };++ // Set up the crawler, passing a single options object as an argument.+ const crawler = new Apify.CheerioCrawler({+ requestQueue,+ handlePageFunction,+ });++ await crawler.run();+});+```++And we're done! You just created your first crawler from scratch. It will download the HTML of `https://apify.com`, find the `<title>` element, get+its text content and print it to console. Good job!++To run the code locally, copy and paste the code, if you haven't already typed it in yourself, to the `main.js` file in the `my-new-project` we+created earlier and run `apify run` from that project's directory.++To run the code on Apify Platform, just replace the original example with your new code and hit Run.++Whichever environment you choose, you should see the message+`The title of "https://apify.com" is: Web Scraping, Data Extraction and Automation - Apify.` printed to the screen. If you do, congratulations and+let's move onto some bigger challenges! And if you feel like you don't really know what just happened there, no worries, it will all become clear when+you learn more about the `CheerioCrawler`.++## CheerioCrawler aka jQuery crawler++This is the crawler that we used in our earlier example. Our simplest and also the fastest crawling solution. If you're familiar with `jQuery`, you'll+understand [`CheerioCrawler`](../api/cheerio-crawler) in minutes. [Cheerio](https://www.npmjs.com/package/cheerio) is+essentially `jQuery` for Node.js. It offers the same API, including the familiar `$` object. You can use it, as you would `jQuery`, for manipulating+the DOM of a HTML page. In crawling, you'll mostly use it to select the right elements and extract their text values - the data you're interested in.+But `jQuery` runs in a browser and attaches directly to the browser's DOM. Where does `cheerio` get its HTML? This is where the `Crawler` part of+[`CheerioCrawler`](../api/cheerio-crawler) comes in.++### Overview++[`CheerioCrawler`](../api/cheerio-crawler) crawls by making plain HTTP requests to the provided URLs. As you remember from the previous section, the+URLs are fed to the crawler using either the [`RequestList`](../api/cheerio-crawler) or the [`RequestQueue`](../api/cheerio-crawler). The HTTP responses+it gets back are HTML pages, the same pages you would get in your browser when you first load a URL.++> Note, however, that modern web pages often do not serve all of their content in the first HTML response, but rather the first HTML contains links to+> other resources such as CSS and JavaScript that get downloaded afterwards and together they create the final page. See our+> [`PuppeteerCrawler`](../api/puppeteer-crawler) to crawl those.++Once the page's HTML is retrieved, the crawler will pass it to [Cheerio](https://www.npmjs.com/package/cheerio) for+parsing. The result is the typical `$` function, which should be familiar to `jQuery` users. You can use this `$` to do all sorts of lookups and+manipulations over the page's HTML, but in scraping, we will mostly use it to find specific HTML elements and extract their data.++Example use of Cheerio and its `$` function in comparison to browser JavaScript:++```js+// Return the text content of the <title> element.+document.querySelector('title').textContent; // plain JS+$('title').text(); // Cheerio++// Return an array of all 'href' links on the page.+Array.from(document.querySelectorAll('[href]')).map(el => el.href); // plain JS+$('[href]')+ .map((i, el) => $(el).attr('href'))+ .get(); // Cheerio+```++> This is not to show that Cheerio is better than plain browser JavaScript. Some might actually prefer the more expressive way plain JS provides.+> Unfortunately, the browser JavaScript methods are not available in Node.js, so Cheerio is our best bet to do the parsing.++### When to use `CheerioCrawler`++Even though using `CheerioCrawler` is extremely easy, it probably will not be your first choice for most kinds of crawling or scraping in production+environments. Since most websites nowadays use modern JavaScript to create rich, responsive and data driven user experiences, the plain HTTP requests+the crawler uses may just fall short of your needs.++But [`CheerioCrawler`](../api/cheerio-crawler) is far from useless! It really shines when you need to do extremely high workloads. With just 4 GBs of memory and a single CPU+core, you can scrape 500 or more pages a minute! _(assuming each page contains approximately 400KB of HTML)_ To get this high with a full browser+scraper, such as the [`PuppeteerCrawler`](../api/puppeteer-crawler), you'd need significantly more computing power.++**Advantages:**++- Extremely fast+- Easy to set up+- Familiar for jQuery users+- Super cheap to run+- Each request can go through a different proxy++**Disadvantages:**++- Does not work for all websites+- May easily overload the target website with requests+- Does not enable any manipulation of the website before scraping++### Basic use of `CheerioCrawler`++Now that we have an idea of the crawler's inner workings, let's build one. We'll use the example from the previous section and improve on it by+letting it truly crawl the page, finding new links as it goes, enqueuing them into the `RequestQueue` and then scraping them.++#### Refresher++Just to refresh your memory, in the previous section we built a very simple crawler that downloads HTML of a single page, reads its title and prints+it to the console. This is the original source code:++```js+const Apify = require('apify');++Apify.main(async () => {+ const requestQueue = await Apify.openRequestQueue();+ await requestQueue.addRequest({ url: 'https://apify.com' });++ const handlePageFunction = async ({ request, $ }) => {+ const title = $('title').text();++ console.log(`The title of "${request.url}" is: ${title}.`);+ };++ // Set up the crawler, passing a single options object as an argument.+ const crawler = new Apify.CheerioCrawler({+ requestQueue,+ handlePageFunction,+ });++ await crawler.run();+});+```++Earlier we said that we would let the crawler:++1. Find new links on the page+2. Filter only those pointing to `apify.com`+3. Enqueue them to the `RequestQueue`+4. Scrape the newly enqueued links++So let's get to it!++#### Finding new links++There are numerous approaches to finding links to follow when crawling the web. For our purposes, we will be looking for `<a>` elements that contain+the `href` attribute. For example `<a href="https://apify.com/store>This is a link to Apify Store</a>`. To do this, we need to update our Cheerio+function.++```js+const links = $('a[href]')+ .map((i, el) => $(el).attr('href'))+ .get();+```++Our new function finds all the `<a>` elements that contain the `href` attribute and extracts the attributes into an array of strings. There is a+problem though. There can be relative links in the list and those can't be used on their own. We need to resolve them using our domain as base URL and+we will use one of Node.js' standard libraries to do this.++```js+// At the top of the file:+const { URL } = require('url');++// ...++const ourDomain = 'https://apify.com';+const absoluteUrls = links.map(link => new URL(link, ourDomain));+```++#### Filtering links to same domain++Websites typically contain a lot of links that lead away from the original page. This is normal, but when crawling a website, we usually want to crawl+this one site and do not let our crawler wander away to Google, Facebook and Twitter. Therefore, we need to filter out the off-domain links and only+keep the ones that lead to the same domain.++> Don't worry, we'll learn how to do this with a single function call using Apify in a few moments.++```js+// At the top of the file:+const { URL } = require('url');++// ...++const links = $('a[href]')+ .map((i, el) => $(el).attr('href'))+ .get();++const ourDomain = 'apify.com';+const absoluteUrls = links.map(link => new URL(link, ourDomain));++const sameDomainLinks = absoluteUrls.filter(url => url.href.startsWith(ourDomain));++// ...+```++#### Enqueueing links to `RequestQueue`++This should be easy, because we already did that [earlier](#putting-it-all-together), remember? Just call `requestQueue.addRequest()` for all the new+links. This will add them to the end of the queue for processing.++```js+// At the top of the file:+const { URL } = require('url');++// ...++const links = $('a[href]')+ .map((i, el) => $(el).attr('href'))+ .get();++const ourDomain = 'https://apify.com';+const absoluteUrls = links.map(link => new URL(link, ourDomain));++const sameDomainLinks = absoluteUrls.filter(url => url.href.startsWith(ourDomain));++// Add the requests in series. There's of course room for speed+// improvement by parallelization. Try to implement it, if you wish.+console.log(`Enqueueing ${sameDomainLinks.length} URLs.`);+for (const url of sameDomainLinks) {+ await requestQueue.addRequest({ url: url.href });+}++// ...+```++#### Scrape the newly enqueued links++And we're approching the finishing line. All we need to do now is just integrate the new code into our original crawler. It will be easy, because+almost everything needs to go into the `handlePageFunction`. But just before we do that, let me introduce the first crawler configuration option, that+is not a `handlePageFunction` or `requestQueue`. It's called `maxRequestsPerCrawl`.++##### The `maxRequestsPerCrawl` limit++This configuration option is available in all crawler classes and you can use it to limit the number of `Requests` the crawler should process. It's+very useful when you're just testing your code or when your crawler could potentially crawl millions of pages and you want to save resources. You can+add it to the crawler options like this:++```js+const crawler = new Apify.CheerioCrawler({+ maxRequestsPerCrawl: 20,+ requestQueue,+ handlePageFunction,+});+```++This limits the number of successfully handled `Requests` to 20. Bear in mind that the actual number of processed requests might be a little higher+and that's because usually there are multiple `Requests` processed at the same time and once the 20th `Request` finishes, the other running `Requests`+will be allowed to finish too.++#### Putting it all together++```js+const { URL } = require('url'); // <------ This is new.+const Apify = require('apify');++Apify.main(async () => {+ const requestQueue = await Apify.openRequestQueue();+ await requestQueue.addRequest({ url: 'https://apify.com' });++ const handlePageFunction = async ({ request, $ }) => {+ const title = $('title').text();+ console.log(`The title of "${request.url}" is: ${title}.`);++ // Here starts the new part of handlePageFunction.+ const links = $('a[href]')+ .map((i, el) => $(el).attr('href'))+ .get();++ const ourDomain = 'https://apify.com';+ const absoluteUrls = links.map(link => new URL(link, ourDomain));++ const sameDomainLinks = absoluteUrls.filter(url => url.href.startsWith(ourDomain));++ console.log(`Enqueueing ${sameDomainLinks.length} URLs.`);+ for (const url of sameDomainLinks) {+ await requestQueue.addRequest({ url: url.href });+ }+ };++ const crawler = new Apify.CheerioCrawler({+ maxRequestsPerCrawl: 20, // <------ This is new too.+ requestQueue,+ handlePageFunction,+ });++ await crawler.run();+});+```++No matter if you followed along with our coding or just copy pasted the resulting source, try running it now, perhaps even in both environments. You+should see the crawler log the **title** of the first page, then the **enqueueing** message showing number of URLs, followed by the **title** of the+first enqueued page and so on and so on.++> If you need help with running the code, refer back to the chapters on environment setup: [Setting up locally](#setting-up-locally) and+> [Setting up on the Apify Platform](#setting-up-on-the-apify-platform).++## Using Apify SDK to enqueue links like a boss++If you were paying attention carefully in the previous chapter, we said that we would show a way to enqueue new `Requests` with a single function+call. You might be wondering why we had to go through the whole process of getting the individual links, filtering the same domain ones and then+manually enqueuing them into the `RequestQueue`, when there is a simpler way.++Well, the obvious reason is practice. This is a tutorial after all. The other reason is to make you think about all the bits and pieces that come+together, so that in the end, a new page, not previously entered in by you, can be scraped. We think that by seeing the bigger picture, you will be+able to get the most out of Apify SDK.++### Meet `Apify.utils`++We will talk at length about them later, but in short, `Apify.utils` is a namespace where you can find various helpful functions and constants that+make your life easier. One of the available functions is `Apify.utils.enqueueLinks()` which encapsulates the whole enqueueing process and even adds+some extra functionality.++### Introduction to `Apify.utils.enqueueLinks()`++Since enqueuing new links to crawl is such an integral part of web crawling, we created a function that attempts to simplify this process as much as+possible. With a single function call, it allows you to find all the links on a page that match specified criteria and add them to a `RequestQueue`.+It also allows you to modify the resulting `Requests` to match your crawling needs.++`enqueueLinks` is quite a powerful function so, like crawlers, it gets its arguments from an options object. This is useful, because you don't have to+remember their order! But also because we can easily extend its API and add new features. You can+[find the full reference here](../api/utils#enqueuelinks).++We suggest using ES6 destructuring to grab the `enqueueLinks()` function off of the `utils` object, so you don't have to type `Apify.utils` all the+time.++```js+const Apify = require('apify');+const {+ utils: { enqueueLinks },+} = Apify;++// Now you can use enqueueLinks like this:+await enqueueLinks({+ /* options */+});+```++### Basic use of `enqueueLinks()` with `CheerioCrawler`++We already implemented logic that takes care of enqueueing new links to a `RequestQueue` in the previous chapter on `CheerioCrawler`. Let's look at+that logic and implement the same functionality using `enqueueLinks()`.++We found that the crawler needed to do these 4 things to crawl `apify.com`:++1. Find new links on the page+2. Filter only those pointing to `apify.com`+3. Enqueue them to the `RequestQueue`+4. Scrape the newly enqueued links++Using `enqueueLinks()` we can squash the first 3 into a single function call, if we set the options correctly. For now, let's just stick to the+basics. At the very least, we need a source where to find the links and the queue to enqueue them to. The `$` Cheerio object is one of the sources the+function accepts and we already know how to work with it in the `handlePageFunction`. We also know how to get a `requestQueue` instance.++```js+// Assuming previous existence of the '$' and 'requestQueue' variables.+await enqueueLinks({ $, requestQueue });+```++That's all we need to do to enqueue all `<a href="...">` links from the given page to the given queue. Easy, right? Scratch number 1 and 3 off the+list. Only number 2 remains and to tackle this one, we need to talk about yet another new concept, the pseudo-URL.++#### Introduction to pseudo-URLs++Pseudo-URLs are represented by our `PseudoUrl` class and even though the name sounds discouraging, they're a pretty simple concept. They're just URLs+with some parts replaced by wildcards (read <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions">regular+expressions</a>). They are matched against URLs to find specific links, domains, patterns, file extensions and so on.++In scraping, there usually are patterns to be found in the websites' URLs that can be leveraged to scrape only the pages we're interested in. Imagine+a typical online store. It has different categories which list different items The URL for might looks something like this:++```+https://www.online-store.com/categories+```++A category would then have a different URL:++```+https://www.online-store.com/categories/computers+```++Going to this page would produce a list of offered computers. Then, clicking on one of the computers might take us to a detail URL:++```+https://www.online-store.com/items/613804+```++As you can see, there's a structure to the links. In the real world, the structure might not always be perfectly obvious, but it's very often there.+Pseudo-URLs help to use this structure to select only the relevant links from a given page.++#### Structure of a pseudo-URL++Pseudo-URL is a URL with [regular expressions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions)) enclosed+in `[]` brackets. Since we're running Node.js, the regular expressions should follow the JavaScript style.++For example, a pseudo-URL++```+https://www.online-store.com/categories/[(\w|-)+]+```++will match all of the following URLs:++```+https://www.online-store.com/categories/computers+https://www.online-store.com/categories/mobile-phones+https://www.online-store.com/categories/black-friday+```++but it will not match++```+https://www.online-store.com/categories+https://www.online-store.com/items/613804+```++This way, you can easily find just the URLs that you're looking for while ignoring the rest.++A pseudo-URL may include any number of bracketed regular expressions, so you can compose much more complex matching logic. The following Pseudo URL+will match the items in the store even if the links use the non-secure `http` protocol, omit the `www` from the hostname or use different TLD.++```+http[s?]://[(www)?\.]online-store.[com|net|org]/items/[\d+]+```++will match any combination of:++```+http://www.online-store.org/items/12345+https://online-store.com/items/633423+http://online-store.net/items/7003+```++but it will not match:++```+http://shop.online-store.org/items/12345+https://www.online-store.com/items/calculator+www.online-store.org/items/7003+```++> Pssst! Don't tell anyone, but you can create `PseudoUrls` with plain old `RegExp` instances instead of this brackety madness as well.++#### Using `enqueueLinks()` to filter links++That's been quite a lot of theory and examples. We might as well put it to practice. Going back to our `CheerioCrawler` exercise, we still have number+2 left to cross off the list - filter links pointing to `apify.com`. We've already shown that at the very least, the `enqueueLinks()` function needs+two arguments. The source, in our case the `$` object, and the destination - the `requestQueue`. To filter links, we need to add a third argument:+`pseudoUrls`.++The `options.pseudoUrls` argument is always an `Array`, but its contents can take on many forms. [See the reference](../api/utils#enqueueLinks)+for all of them. Since we just need to filter out same domain links, we'll keep it simple and use a pseudo-URL `string`.++```js+// Assuming previous existence of the '$' and 'requestQueue' variables.+const options = {+ $,+ requestQueue,+ pseudoUrls: ['http[s?]://apify.com[.*]'],+};++await enqueueLinks(options);+```++> To break the pseudo-URL string down, we're looking for both `http` and `https` protocols and the links may only lead to `apify.com` domain. The+> final brackets `[.*]` allow everything, so `apify.com/contact` as well as `apify.com/store` will match. If this is complex to you, we suggest+> [reading a tutorial](https://www.regular-expressions.info/tutorial.html) or two on regular expression syntax.++#### Resolving relative URLs with `enqueueLinks()`++**TLDR;** Just use `baseUrl: request.loadedUrl` when working with `CheerioCrawler`.++This is probably the weirdest and most complicated addition to the list. This is not the place to talk at length about+[absolute and relative paths](https://stackoverflow.com/questions/2005079/absolute-vs-relative-urls), but in short, the+links we encounter in a page can either be absolute, such as:++```+https://apify.com/john-doe/my-actor+```++or relative:++```+./john-doe/my-actor+```++Browsers handle this automatically, but since we're only using plain HTTP requests, we need to tell the `enqueueLinks()` function how to resolve the+relative links to the absolute ones, so we can use them for scraping. This is where the `request.loadedUrl` comes into play, because it returns the+correct URL to use as `baseUrl`.++```js+// Assuming previous existence of the '$', 'requestQueue' and 'request' variables.+const options = {+ $,+ requestQueue,+ pseudoUrls: ['http[s?]://apify.com[.*]'],+ baseUrl: request.loadedUrl,+};++await enqueueLinks(options);+```++> Even though it seems possible, we can't use the `request.url` of our `Request` instances, because the page could have been redirected and the final+> URL would be different from the one we requested.++#### Integrating `enqueueLinks()` into our crawler++That was fairly easy, wasn't it. That ticks the number 2 off our list and we're done! Let's take a look at the original crawler code, where we+enqueued all the links manually.++```js+const { URL } = require('url'); // <------ This is new.+const Apify = require('apify');++Apify.main(async () => {+ const requestQueue = await Apify.openRequestQueue();+ await requestQueue.addRequest({ url: 'https://apify.com' });++ const handlePageFunction = async ({ request, $ }) => {+ const title = $('title').text();+ console.log(`The title of "${request.url}" is: ${title}.`);++ // Here starts the new part of handlePageFunction.+ const links = $('a[href]')+ .map((i, el) => $(el).attr('href'))+ .get();++ const ourDomain = 'https://apify.com';+ const absoluteUrls = links.map(link => new URL(link, ourDomain));++ const sameDomainLinks = absoluteUrls.filter(url => url.href.startsWith(ourDomain));++ console.log(`Enqueueing ${sameDomainLinks.length} URLs.`);+ for (const url of sameDomainLinks) {+ await requestQueue.addRequest({ url: url.href });+ }+ };++ const crawler = new Apify.CheerioCrawler({+ maxRequestsPerCrawl: 20, // <------ This is new too.+ requestQueue,+ handlePageFunction,+ });++ await crawler.run();+});+```++Since we've already prepared the `enqueueLinks()` options, we can just replace all the above enqueuing logic with a single function call, as promised.++```js+const Apify = require('apify');+const {+ utils: { enqueueLinks },+} = Apify;++Apify.main(async () => {+ const requestQueue = await Apify.openRequestQueue();+ await requestQueue.addRequest({ url: 'https://apify.com' });++ const handlePageFunction = async ({ request, $ }) => {+ const title = $('title').text();+ console.log(`The title of "${request.url}" is: ${title}.`);++ // Enqueue links+ const enqueued = await enqueueLinks({+ $,+ requestQueue,+ pseudoUrls: ['http[s?]://apify.com[.*]'],+ baseUrl: request.loadedUrl,+ });+ console.log(`Enqueued ${enqueued.length} URLs.`);+ };++ const crawler = new Apify.CheerioCrawler({+ maxRequestsPerCrawl: 20,+ requestQueue,+ handlePageFunction,+ });++ await crawler.run();+});+```++And that's it! No more parsing the links from HTML using Cheerio, filtering them and enqueueing them one by one It all gets done automatically!+`enqueueLinks()` is just one example of Apify SDK's powerful helper functions. They're all designed to make your life easier so you can focus on+getting your data, while leaving the mundane crawling management to your tools.++`Apify.utils.enqueueLinks()` has a lot more tricks up its sleeve. Make sure to check out the+[reference documentation](../api/utils#enqueueLinks) to see what else it can do for you. Namely the feature to prepopulate the `Request`+instances it creates with `userData` of your choice is extremely useful!++## Getting some real world data++> Hey, guys, you know, it's cool that we can scrape the `<title>` elements of web pages, but that's not very useful. Can we finally scrape some real+> data and save it somewhere in a machine readable format? Because that's why started reading this tutorial in the first place!++We hear you young padawan! First, learn how to crawl, you must. Only then, walk through data, you can!++### Making a store crawler++Fortunately, we don't have to travel to a galaxy far far away to find a good candidate for learning how to scrape+structured data. The [Apify Store](https://apify.com/store) is a store of public actors that anyone can grab and use. You+can find ready-made solutions for crawling [Google Places](https://apify.com/drobnikj/crawler-google-places),+[Amazon](https://apify.com/vaclavrut/amazon-crawler),+[Google Search](https://apify.com/apify/google-search-scraper),+[Booking](https://apify.com/dtrungtin/booking-scraper),+[Instagram](https://apify.com/jaroslavhejlek/instagram-scraper),+[Tripadvisor](https://apify.com/maxcopell/tripadvisor) and many other websites. Feel free to check them out! It+also poses a great place to practice our jedi scraping skills since it has categories, lists and details. That's almost like our imaginary+`online-store.com` from the previous chapter.++### The importance of having a plan++Sometimes scraping is really straightforward, but most of the times, it really pays out to do a little bit of research first. How is the website+structured? Can I scrape it only with HTTP requests (read "with `CheerioCrawler`") or would I need a full browser solution? Are there any+anti-scraping protections in place? Do I need to parse the HTML or can I get the data otherwise, such as directly from the website's API. Jakub,+one of Apify's founders wrote a+[great article about all the different techniques](https://blog.apify.com/web-scraping-in-2018-forget-html-use-xhrs-metadata-or-javascript-variables-8167f252439c)+and tips and tricks so make sure to check that out!++For the purposes of this tutorial, let's just go ahead with HTTP requests and HTML parsing using `CheerioCrawler`. The number one reason being: We+already know how to use it and we want to build on that knowledge to learn specific crawling and scraping techniques.++#### Choosing the data we need++A good first step is always to figure out what it is we want to scrape and where to find it. For the time being, let's just agree that we want to+scrape all actors (see the `Show` dropdown) in all categories (which can be found on the left side of the page) and for each actor we want to get its++1. URL+2. Owner+3. Unique identifier (such as `apify/web-scraper`)+4. Title+5. Description+6. Last modification date+7. Number of runs++We can see that some of the information is available directly on the list page, but for details such as "Last modification date" or "Number of runs" we'll need+to open the actor detail pages too.++++#### Analyzing the target++Knowing that we will use plain HTTP requests, we immediately know that we won't be able to manipulate the website in any way. We will only be able to+go through the HTML it gives us and parse our data from there. This might sound like a huge limitation, but you might be surprised in how effective it+might be. Let's get on it!++#### The start URL(s)++This is where we start our crawl. It's convenient to start as close to our data as possible. For example, it wouldn't make much sense to start at+`apify.com` and look for a `store` link there, when we already know that everything we want to extract can be found at the `apify.com/store` page.++Once we look at the `apify.com/store` page more carefully though, we see that the categories themselves produce URLs that we can use to access those+individual categories.++```+https://apify.com/store?category=ENTERTAINMENT+```++Should we write down all the category URLs down and use all of them as start URLs? It's definitely possible, but what if a new category appears on the+page later? We would not learn about it unless we manually visit the page and inspect it again. So scraping the category links off the store page+definitely makes sense. This way we always get an up to date list of categories.++But is it really that straightforward? By digging further into the store page's HTML we find that it does not actually contain the category links. The+menu on the left uses JavaScript to display the items from a given category and, as we've learned earlier, `CheerioCrawler` cannot execute JavaScript.++> We've deliberately chosen this scenario to show an example of the number one weakness of `CheerioCrawler`. We will overcome this difficulty in our+> `PuppeteerCrawler` tutorial, but at the cost of compute resources and speed. Always remember that no tool is best for everything!++So we're back to the pre-selected list of URLs. Since we cannot scrape the list dynamically, we have to manually collect the links and then use them+in our crawler. We lose the ability to scrape new categories, but we keep the low resource consumption and speed advantages of `CheerioCrawler`.++Therefore, after careful consideration, we've determined that we should use multiple start URLs and that they should look as follows:++```+https://apify.com/store?category=TRAVEL+https://apify.com/store?category=ECOMMERCE+https://apify.com/store?category=ENTERTAINMENT+```++### The crawling strategy++Now that we know where to start, we need to figure out where to go next. Since we've eliminated one level of crawling by selecting the categories+manually, we only need to crawl the actor detail pages now. The algorithm therefore follows:++1. Visit the category list page (one of our start URLs).+2. Enqueue all links to actor details.+3. Visit all actor details and extract data.+4. Repeat 1 - 3 for all categories.++> Technically, this is a depth first crawl and the crawler will perform a breadth first crawl by default, but that's an implementation detail. We've+> chosen this notation since a breadth first crawl would be less readable.++`CheerioCrawler` will make sure to visit the pages for us, if we provide the correct `Requests` and we already know how to enqueue pages, so this+should be fairly easy. Nevertheless, there are two more tricks that we'd like to show you.++#### Using a `RequestList`++`RequestList` is a perfect tool for scraping a pre-existing list of URLs and if you think about our start URLs, this is exactly what we have! A list+of links to the different categories of the store. Let's see how we'd get them into a `RequestList`.++```js+const sources = [+ 'https://apify.com/store?category=TRAVEL',+ 'https://apify.com/store?category=ECOMMERCE',+ 'https://apify.com/store?category=ENTERTAINMENT',+];++const requestList = await Apify.openRequestList('categories', sources);+```++As you can see, similarly to the `Apify.openRequestQueue()` function, there is an `Apify.openRequestList()` function that will create a `RequestList`+instance for you. The first argument is a name of the `RequestList`. It is used to persist the crawling state of the list. This is useful when you+want to continue where you left off after an error or a process restart. The second argument is the `sources` array, which is nothing more than a list+of URLs you wish to crawl.++> `RequestQueue` is a persistent store by default, so no name is needed, while the `RequestList` only lives in memory and giving it a name enables it+> to become persistent.++You might now want to ask one of the below questions:++- Can I enqueue into `RequestList` too?+- How do I make `RequestList` work together with `RequestQueue` since I need the queue to enqueue new `Requests`.++The answer to the first one is a definitive no. `RequestList` is immutable and once you create it, you cannot add or remove `Requests` from it. The+answer to the second one is simple. `RequestList` and `RequestQueue` are made to work together out of the box in crawlers, so all you need to do is+use them both and the crawlers will do the rest.++```js+const crawler = new Apify.CheerioCrawler({+ requestList,+ requestQueue,+ handlePageFunction,+});+```++> For those wondering how this works, the `RequestList` `Requests` are enqueued into the `RequestQueue` right before their execution and only+> processed by the `RequestQueue` afterwards. You can, of course, enqueue the `Requests` to the queue manually, but that would take some boilerplate+> code and perhaps quite a long time, if we were talking about tens of thousands or more `Requests`. The crawlers do it while running, so the time to+> enqueue is spread out and you won't even notice it.++#### Sanity check++It's always useful to create some simple boilerplate code to see that we've got everything set up correctly before we start to write+the scraping logic itself. We might realize that something in our previous analysis doesn't quite add up, or the website might not behave exactly the+same as we expected.++Let's use the newly acquired `RequestList` knowledge and everything we know from the previous chapters to create a new crawler that'll just visit all+the category URLs we selected and print the text content of all the actors in the category. Try running the code below in your selected environment.+You should see, albeit very badly formatted, the text of the individual actor cards that are displayed in the selected categories.++```js+const Apify = require('apify');++Apify.main(async () => {+ const sources = [+ 'https://apify.com/store?category=TRAVEL',+ 'https://apify.com/store?category=ECOMMERCE',+ 'https://apify.com/store?category=ENTERTAINMENT',+ ];++ const requestList = await Apify.openRequestList('categories', sources);++ const crawler = new Apify.CheerioCrawler({+ requestList,+ handlePageFunction: async ({ $, request }) => {+ // Select all the actor cards.+ $('.item').each((i, el) => {+ const text = $(el).text();+ console.log(`ITEM: ${text}\n`);+ });+ },+ });++ await crawler.run();+});+```++> If there's anything you don't understand, refer to the previous chapters on setting up your environment, building your first crawler and+> `CheerioCrawler`.++You might be wondering how we got that `.item` selector. After analyzing the category pages using a browser's DevTools, we've determined that it's a+good selector to select all the currently displayed actor cards. DevTools and CSS selectors are quite a large topic, so we can't go into too much+detail here, but here are a few general pointers.++#### DevTools crash course++> We'll use Chrome DevTools here, since it's the most common browser, but feel free to use any other, it's all very similar.++We could pick any category, but let's just go with Travel because it includes some interesting actors. Go to++```+https://apify.com/store?category=TRAVEL+```++and open DevTools either by right clicking anywhere in the page and selecting `Inspect`, or by pressing `F12` or by any other means relevant to your+system. Once you're there, you'll see a bunch of DevToolsy stuff and a view of the category page with the individual actor cards.++Now, find the `Select an element` tool and use it to select one of the actor cards. Make sure to select the whole card, not some of its contents, such+as its title or description.++In the resulting HTML display, it will put your cursor somewhere. Inspect the HTML around it. You'll see that there are CSS classes attached to the+different HTML elements.++By hovering over the individual elements, you will see their placement in the page's view. It's easy to see the page's structure around the actor+cards now. All the cards are displayed in a `<div>` with a classname that starts with `ItemsGrid__StyledDiv`, which holds another `<div>` with some+computer generated class names and finally, inside this `<div>`, the individual cards are represented by other `<div>` elements with the class of+`item`.++> Yes, there are other HTML elements and other classes too. We can safely ignore them.++It should now make sense how we got that `.item` selector. It's just a selector that finds all elements that are annotated with the `item` class and+those just happen to be the actor cards only.++It's always a good idea to double check that though, so go into the DevTools Console and run++```js+document.querySelectorAll('.item');+```++You will see that only the actor cards will be returned, and nothing else.++#### Enqueueing the detail links using a custom selector++In the previous chapter, we've used the `Apify.utils.enqueueLinks()` function like this:++```js+await enqueueLinks({+ $,+ requestQueue,+ pseudoUrls: ['http[s?]://apify.com[.*]'],+ baseUrl: request.loadedUrl,+});+```++While very useful in that scenario, we need something different now. Instead of finding all the `<a href="..">` links that match the `pseudoUrl`, we+need to find only the specific ones that will take us to the actor detail pages. Otherwise, we'd be visiting a lot of other pages that we're not+interested in. Using the power of DevTools and yet another `enqueueLinks()` parameter, this becomes fairly easy.++```js+const handlePageFunction = async ({ $, request }) => {+ console.log(`Processing ${request.url}`);++ // Only enqueue new links from the category pages.+ if (!request.userData.detailPage) {+ await Apify.utils.enqueueLinks({+ $,+ requestQueue,+ selector: 'div.item > a',+ baseUrl: request.loadedUrl,+ transformRequestFunction: req => {+ req.userData.detailPage = true;+ return req;+ },+ });+ }+};+```++The code should look pretty familiar to you. It's a very simple `handlePageFunction` where we log the currently processed URL to the console and+enqueue more links. But there are also a few new, interesting additions. Let's break it down.++##### The `selector` parameter of `enqueueLinks()`++When we previously used `enqueueLinks()`, we were not providing any `selector` parameter and it was fine, because we wanted to use the default+setting, which is `a` - finds all `<a>` elements. But now, we need to be more specific. There are multiple `<a>` links on the given category page, but+we're only interested in those that will take us to item (actor) details. Using the DevTools, we found out that we can select the links we wanted+using the `div.item > a` selector, which selects all the `<a>` elements that have a `<div class="item ...">` parent. And those are exactly the ones+we're interested in.++##### The missing `pseudoUrls`++Earlier we've learned that `pseudoUrls` are not required and if omitted, all links matching the given `selector` will be enqueued. This is exactly+what we need, so we're skipping `pseudoUrls` this time. That does not mean that you can't use `pseudoUrls` together with a custom `selector` though,+because you absolutely can!++##### Finally, the `userData` of `enqueueLinks()`++You will see `userData` used often throughout Apify SDK and it's nothing more than a place to store your own data on a `Request` instance. You can+access it by `request.userData` and it's a plain `Object` that can be used to store anything that needs to survive the full life-cycle of the+`Request`.++We can use the `transformRequestFunction` option of `enqueueLinks()` to modify all the `Request` instances it creates and enqueues. In our case, we+use it to set a `detailPage` property to the enqueued `Requests` to be able to easily differentiate between the category pages and the detail pages.++#### Another sanity check++It's always good to work step by step. We have this new enqueueing logic in place and since the previous [Sanity check](#sanity-check) worked only+with a `RequestList`, because we were not enqueueing anything so don't forget to add back the `RequestQueue` and `maxRequestsPerCrawl` limit. Let's+test it out!++```js+const Apify = require('apify');++Apify.main(async () => {+ const sources = [+ 'https://apify.com/store?category=TRAVEL',+ 'https://apify.com/store?category=ECOMMERCE',+ 'https://apify.com/store?category=ENTERTAINMENT',+ ];++ const requestList = await Apify.openRequestList('categories', sources);+ const requestQueue = await Apify.openRequestQueue(); // <----------------++ const crawler = new Apify.CheerioCrawler({+ maxRequestsPerCrawl: 50, // <----------------------------------------+ requestList,+ requestQueue, // <---------------------------------------------------+ handlePageFunction: async ({ $, request }) => {+ console.log(`Processing ${request.url}`);++ // Only enqueue new links from the category pages.+ if (!request.userData.detailPage) {+ await Apify.utils.enqueueLinks({+ $,+ requestQueue,+ selector: 'div.item > a',+ baseUrl: request.loadedUrl,+ transformRequestFunction: req => {+ req.userData.detailPage = true;+ return req;+ },+ });+ }+ },+ });++ await crawler.run();+});+```++We've added the `handlePageFunction()` with the `enqueueLinks()` logic from the previous section to the code we've written earlier. As always, try+running it in an environment of your choice. You should see the crawler output a number of links to the console, as it crawls the category pages first+and then all the links to the actor detail pages it found.++This concludes our Crawling strategy section, because we have taught the crawler to visit all the pages we need. Let's continue with scraping the+tasty data.++### Scraping data++At the beginning of this chapter, we've created a list of information we wanted to collect about the actors in the store. Let's review that and figure+out ways to access it.++1. URL+2. Owner+3. Unique identifier (such as `apify/web-scraper`)+4. Title+5. Description+6. Last modification date+7. Number of runs++++#### Scraping the URL, Owner and Unique identifier++Some information is lying right there in front of us without even having to touch the actor detail pages. The `URL` we already have - the+`request.url`. And by looking at it carefully, we realize that it already includes the `owner` and the `unique identifier` too. We can just split the+`string` and be on our way then!++```js+// request.url = https://apify.com/apify/web-scraper++const urlArr = request.url.split('/').slice(-2); // ['apify', 'web-scraper']+const uniqueIdentifier = urlArr.join('/'); // 'apify/web-scraper'+const owner = urlArr[0]; // 'apify'+```++> It's always a matter of preference, whether to store this information separately in the resulting dataset, or not. Whoever uses the dataset can+> easily parse the `owner` from the `URL`, so should we duplicate the data unnecessarily? Our opinion is that unless the increased data consumption+> would be too large to bear, it's always better to make the dataset as readable as possible. Someone might want to filter by `owner` for example and+> keeping only the `URL` in the dataset would make this complicated without using additional tools.++#### Scraping Title, Description, Last modification date and Number of runs++Now it's time to add more data to the results. Let's open one of the actor detail pages in the Store, for example the+[`apify/web-scraper`](https://apify.com/apify/web-scraper) page and use our DevTools-Fu to figure out how to get the title of the actor.++##### Title++++By using the element selector tool, we find out that the title is there under an `<h1>` tag, as titles should be.+Maybe surprisingly, we find that there are actually two `<h1>` tags on the detail page. This should get us thinking.+Is there any parent element that includes our `<h1>` tag, but not the other ones? Yes, there is! There is a `<header>`+element that we can use to select only the heading we're interested in.++> Remember that you can press CTRL+F (CMD+F) in the Elements tab of DevTools to open the search bar where you can quickly search for elements using+> their selectors. And always make sure to use the DevTools to verify your scraping process and assumptions. It's faster than changing the crawler+> code all the time.++To get the title we just need to find it using `Cheerio` and a `header h1` selector, which selects all `<h1>` elements that have a `<header>` ancestor.+And as we already know, there's only one.++```js+return {+ title: $('header h1').text(),+};+```++##### Description++Getting the actor's description is a little more involved, but still pretty straightforward. We can't just simply search for a `<p>` tag, because+there's a lot of them in the page. We need to narrow our search down a little. Using the DevTools we find that the actor description is nested within+the `<header>` element too, same as the title. Moreover, the actual description is nested inside a `<span>` tag with a class `actor-description`.++++```js+return {+ title: $('header h1').text(),+ description: $('header span.actor-description').text(),+};+```++##### Last modification date++The DevTools tell us that the `modifiedDate` can be found in the `<time>` element inside `<ul class="ActorHeader-stats">`.++++```js+return {+ title: $('header h1').text(),+ description: $('header span.actor-description').text(),+ modifiedDate: new Date(+ Number(+ $('ul.ActorHeader-stats time').attr('datetime'),+ ),+ ),+};+```++It might look a little too complex at first glance, but let me walk you through it. We find the right `<time>` element,+and then we read its `datetime` attribute, because that's where a unix timestamp is stored as a `string`.++But we would much rather see a readable date in our results, not a unix timestamp, so we need to convert it. Unfortunately the `new Date()`+constructor will not accept a `string`, so we cast the `string` to a `number` using the `Number()` function before actually calling `new Date()`.+Phew!++##### Run count++And so we're finishing up with the `runCount`. There's no specific element like `<time>`, so we need to create a complex selector and then do a+transformation on the result.++```js+return {+ title: $('header h1').text(),+ description: $('header span.actor-description').text(),+ modifiedDate: new Date(+ Number(+ $('ul.ActorHeader-stats time').attr('datetime'),+ ),+ ),+ runCount: Number(+ $('ul.ActorHeader-stats > li:nth-of-type(3)')+ .text()+ .match(/[\d,]+/)[0]+ .replace(',', ''),+ ),+};+```++The `ul.ActorHeader-stats > li:nth-of-type(3)` looks complicated, but it only reads that we're looking for a `<ul class="ActorHeader-stats ...">` element and within that+element we're looking for the third `<li>` element. We grab its text, but we're only interested in the number of runs. So we parse the number out+using a regular expression, but its type is still a `string`, so we finally convert the result to a `number` by wrapping it with a `Number()` call.++> The numbers are formatted with commas as thousands separators (e.g. `'1,234,567'`), so to extract it, we+> first use regular expression `/[\d,]+/` - it will search for consecutive number or comma characters.+> Then we extract the match via `.match(/[\d,]+/)[0]` and finally remove the commas by calling `.replace(',', '')`.+> This will give us a string (e.g. `'1234567'`) that can be converted via `Number` function.++And there we have it! All the data we needed in a single object. For the sake of completeness, let's add the properties we parsed from the URL earlier+and we're good to go.++```js+const urlArr = request.url.split('/').slice(-2);++const results = {+ url: request.url,+ uniqueIdentifier: urlArr.join('/'),+ owner: urlArr[0],+ title: $('header h1').text(),+ description: $('header span.actor-description').text(),+ modifiedDate: new Date(+ Number(+ $('ul.ActorHeader-stats time').attr('datetime'),+ ),+ ),+ runCount: Number(+ $('ul.ActorHeader-stats > li:nth-of-type(3)')+ .text()+ .match(/[\d,]+/)[0]+ .replace(',', ''),+ ),+};++console.log('RESULTS: ', results);+```++#### Trying it out (sanity check #3)++We have everything we need so just grab our newly created scraping logic, dump it into our original `handlePageFunction()` and see the magic!++```js+const Apify = require('apify');++Apify.main(async () => {+ const sources = [+ 'https://apify.com/store?category=TRAVEL',+ 'https://apify.com/store?category=ECOMMERCE',+ 'https://apify.com/store?category=ENTERTAINMENT',+ ];++ const requestList = await Apify.openRequestList('categories', sources);+ const requestQueue = await Apify.openRequestQueue();++ const crawler = new Apify.CheerioCrawler({+ maxRequestsPerCrawl: 50,+ requestList,+ requestQueue,+ handlePageFunction: async ({ $, request }) => {+ console.log(`Processing ${request.url}`);++ // This is our new scraping logic.+ if (request.userData.detailPage) {+ const urlArr = request.url.split('/').slice(-2);++ const results = {+ url: request.url,+ uniqueIdentifier: urlArr.join('/'),+ owner: urlArr[0],+ title: $('header h1').text(),+ description: $('header span.actor-description').text(),+ modifiedDate: new Date(+ Number(+ $('ul.ActorHeader-stats time').attr('datetime'),+ ),+ ),+ runCount: Number(+ $('ul.ActorHeader-stats > li:nth-of-type(3)')+ .text()+ .match(/[\d,]+/)[0]+ .replace(',', ''),+ ),+ };+ console.log('RESULTS', results);+ }++ // Only enqueue new links from the category pages.+ if (!request.userData.detailPage) {+ await Apify.utils.enqueueLinks({+ $,+ requestQueue,+ selector: 'div.item > a',+ baseUrl: request.loadedUrl,+ transformRequestFunction: req => {+ req.userData.detailPage = true;+ return req;+ },+ });+ }+ },+ });++ await crawler.run();+});+```++> Notice again that we're scraping on the detail pages `request.userData.detailPage === true`, but we're only enqueueing on the category pages+> `request.userData.detailPage === undefined`.++When running the actor in an environment of your choice, you should see the crawled URLs and their scraped data printed to the console.++### Saving the scraped data++A data extraction job would not be complete without saving the data for later use and processing. We've come to the final and most difficult part of+this chapter so make sure to pay attention very carefully!++First, replace the `console.log('RESULTS', results)` call with++```js+await Apify.pushData(results);+```++and that's it. Unlike in the previous paragraph, I'm serious now. That's it, we're done. The final code therefore looks exactly like this:++```js+const Apify = require('apify');++Apify.main(async () => {+ const sources = [+ 'https://apify.com/store?category=TRAVEL',+ 'https://apify.com/store?category=ECOMMERCE',+ 'https://apify.com/store?category=ENTERTAINMENT',+ ];++ const requestList = await Apify.openRequestList('categories', sources);+ const requestQueue = await Apify.openRequestQueue();++ const crawler = new Apify.CheerioCrawler({+ maxRequestsPerCrawl: 50,+ requestList,+ requestQueue,+ handlePageFunction: async ({ $, request }) => {+ console.log(`Processing ${request.url}`);++ // This is our new scraping logic.+ if (request.userData.detailPage) {+ const urlArr = request.url.split('/').slice(-2);++ const results = {+ url: request.url,+ uniqueIdentifier: urlArr.join('/'),+ owner: urlArr[0],+ title: $('header h1').text(),+ description: $('header span.actor-description').text(),+ modifiedDate: new Date(+ Number(+ $('ul.ActorHeader-stats time').attr('datetime'),+ ),+ ),+ runCount: Number(+ $('ul.ActorHeader-stats > li:nth-of-type(3)')+ .text()+ .match(/[\d,]+/)[0]+ .replace(',', ''),+ ),+ };+ await Apify.pushData(results);+ }++ // Only enqueue new links from the category pages.+ if (!request.userData.detailPage) {+ await Apify.utils.enqueueLinks({+ $,+ requestQueue,+ selector: 'div.item > a',+ baseUrl: request.loadedUrl,+ transformRequestFunction: req => {+ req.userData.detailPage = true;+ return req;+ },+ });+ }+ },+ });++ await crawler.run();+});+```++#### What's `Apify.pushData()`++[`Apify.pushData()`](../api/apify#pushdata) is a helper function that saves data to the default [`Dataset`](../api/dataset). `Dataset` is a+storage designed to hold virtually unlimited amount of data in a format similar to a table. Each time you call `Apify.pushData()` a new row in the+table is created, with the property names serving as column titles.++> Each actor run has one default `Dataset` so no need to initialize it or create an instance first. It just gets done automatically for you. You can+> also create named datasets at will.++#### Finding my saved data++It might not be perfectly obvious where the data we saved using the previous command went, so let's break it down by environment:++##### Dataset on the Apify Platform++Open any Run of your actor on the Platform and you will see a Dataset as one of the available tabs. Clicking on it will reveal basic information about+the Dataset and a list of options that you can use to download your data. There are various formats such as JSON, XLSX or CSV available and there's+also the possibility of downloading only Clean items, i.e. a filtered dataset with empty rows and hidden fields removed.++##### Local Dataset++Unless you changed the environment variables that Apify SDK uses locally, which would suggest that you knew what you were doing and you didn't need+this tutorial anyway, you'll find your data in your local Apify Storage.++```+{PROJECT_FOLDER}/apify_storage/datasets/default/+```++The above folder will hold all your saved data in numbered files, as they were pushed into the dataset. Each file represents one invocation of+`Apify.pushData()` or one table row.++> Unfortunately, the local datasets don't yet support the export in various formats functionality that the Platform Dataset page offers, so for the+> time being, we're stuck with JSON.++### Final touch++It may seem that the data are extracted and the actor is done, but honestly, this is just the beginning. For the sake of brevity, we've completely+omitted error handling, proxies, debug logging, tests, documentation and other stuff that a reliable software should have. The good thing is, **error+handling is mostly done by Apify SDK itself**, so no worries on that front, unless you need some custom magic.++Anyway, to spark some ideas, let's look at two more things. First, passing an input to the actor, which will enable us to change the categories we+want to scrape without changing the source code itself! And then some refactoring, to show you how we reckon is preferable to structure and annotate+actor code.++#### Meet the `INPUT`++`INPUT` is just a convention on how we call the actor's input. Because there's no magic in actors, just features, the `INPUT` is actually nothing more+than a key in the default [`KeyValueStore`](../api/key-value-store) that's, by convention, used as input on Apify Platform. Also by convention, the+`INPUT` is mostly expected to be of `Content-Type: application/json`.++We will not go into `KeyValueStore` details here, but for the sake of `INPUT` you need to remember that there is a function that helps you get it.++```js+const input = await Apify.getInput();+```++On the Apify Platform, the actor's input that you can set in the Console is automatically saved to the default `KeyValueStore` under the key `INPUT`+and by calling [`Apify.getInput()`](../api/apify#getvalue) you retrieve the value from the `KeyValueStore`.++Running locally, you need to place an `INPUT.json` file in your default key value store for this to work.++```+{PROJECT_FOLDER}/apify_storage/key_value_stores/default/INPUT.json+```++#### Use `INPUT` to seed our actor with categories++Currently we're using the full URLs of categories as sources, but it's quite obvious that we only need the final parameters, the rest of the URL is+always the same. Knowing that, we can pass an array of those parameters on `INPUT` and build the URLs dynamically, which would allow us to scrape+different categories without changing the source code. Let's get to it!++First, we set up our `INPUT`, either in the `INPUT` form of the actor on Apify Platform, or by creating an `INPUT.json` in our default key value store+locally.++```json+["TRAVEL", "ECOMMERCE", "ENTERTAINMENT"]+```++Once we have that, we can load it in the actor and populate the crawler's sources with it. In the following example, we're using the categories in the+input to construct the category URLs and we're also passing custom `userData` to the sources. This means that the `Requests` that get created will+automatically contain this `userData`.++```js+// ...+const input = await Apify.getInput();++const sources = input.map(category => ({+ url: `https://apify.com/store?category=${category}`,+ userData: {+ label: 'CATEGORY',+ },+}));++const requestList = await Apify.openRequestList('categories', sources);+// ...+```++The `userData.label` is also a convention that we've been using for quite some time to label different `Requests`. We know that this is a category URL+so we `label` it `CATEGORY`. This way, we can easily make decisions in the `handlePageFunction` without having to inspect the URL itself.++We can then refactor the `if` clauses in the `handlePageFunction` to use the `label` for decision making. This does not make much sense for a crawler+with only two different pages, because a simple `boolean` would suffice, but for pages with multiple different views, it becomes very useful.++#### Structuring the code better++But perhaps we should not stop at refactoring the `if` clauses. There are several ways we can make the actor look more elegant and - most+importantly - easier to reason about and make changes to.++In the following code we've made several changes.++- Split the code into multiple files.+- Added the `Apify.utils.log` and replaced `console.log` with it.+- Added a `getSources()` function to encapsulate `INPUT` consumption.+- Added a `createRouter()` function to make our routing cleaner, without nested `if` clauses.+- Removed the `maxRequestsPerCrawl` limit.++> To create a multi-file actor on the Apify Platform, select **Multiple source files** in the **Type** dropdown on the **Source** screen.++In our `main.js` file, we place the general structure of the crawler:++```js+// main.js+const Apify = require('apify');+const tools = require('./tools');+const {+ utils: { log },+} = Apify;++Apify.main(async () => {+ log.info('Starting actor.');+ const requestList = await Apify.openRequestList('categories', await tools.getSources());+ const requestQueue = await Apify.openRequestQueue();+ const router = tools.createRouter({ requestQueue });++ log.debug('Setting up crawler.');+ const crawler = new Apify.CheerioCrawler({+ requestList,+ requestQueue,+ handlePageFunction: async context => {+ const { request } = context;+ log.info(`Processing ${request.url}`);+ await router(request.userData.label, context);+ },+ });++ log.info('Starting the crawl.');+ await crawler.run();+ log.info('Actor finished.');+});+```++Then in a separate `tools.js`, we add our helper functions:++```js+// tools.js+const Apify = require('apify');+const routes = require('./routes');+const {+ utils: { log },+} = Apify;++exports.getSources = async () => {+ log.debug('Getting sources.');+ const input = await Apify.getInput();+ return input.map(category => ({+ url: `https://apify.com/store?category=${category}`,+ userData: {+ label: 'CATEGORY',+ },+ }));+};++exports.createRouter = globalContext => {+ return async function(routeName, requestContext) {+ const route = routes[routeName];+ if (!route) throw new Error(`No route for name: ${routeName}`);+ log.debug(`Invoking route: ${routeName}`);+ return route(requestContext, globalContext);+ };+};+```++And finally our routes in a separate `routes.js` file:++```js+// routes.js+const Apify = require('apify');+const {+ utils: { log },+} = Apify;++exports.CATEGORY = async ({ $, request }, { requestQueue }) => {+ return Apify.utils.enqueueLinks({+ $,+ requestQueue,+ selector: 'div.item > a',+ baseUrl: request.loadedUrl,+ transformRequestFunction: req => {+ req.userData.label = 'DETAIL';+ return req;+ },+ });+};++exports.DETAIL = async ({ $, request }) => {+ const urlArr = request.url.split('/').slice(-2);++ log.debug('Scraping results.');+ const results = {+ url: request.url,+ uniqueIdentifier: urlArr.join('/'),+ owner: urlArr[0],+ title: $('header h1').text(),+ description: $('header span.actor-description').text(),+ modifiedDate: new Date(+ Number(+ $('ul.ActorHeader-stats time').attr('datetime'),+ ),+ ),+ runCount: Number(+ $('ul.ActorHeader-stats > li:nth-of-type(3)')+ .text()+ .match(/[\d,]+/)[0]+ .replace(',', ''),+ ),+ };++ log.debug('Pushing data to dataset.');+ await Apify.pushData(results);+};+```++Let us tell you a little bit more about the changes. We're hopeful that in the end, you'll agree that this structure makes the actor more readable and+manageable.++#### Splitting your code into multiple files++It was not always the case, but now that Apify Platform has a multifile editor, there's no reason not to split your code into multiple files and keep+your logic separate. Less code in a single file means less code you need to think about at any time, and that's a great thing!++#### Using `Apify.utils.log` instead of `console.log`++We wont go into great lengths here to talk about `utils.log` here, because you can read [it all in the documentation](../api/log), but there's just+one thing that we need to stress: **log levels**.++`utils.log` enables you to use different log levels, such as `log.debug`, `log.info` or `log.warning`. It not only makes your log more readable, but+it also allows selective turning off of some levels by either calling the `utils.log.setLevel()` function or by setting an `APIFY_LOG_LEVEL` variable.+This is huge! Because you can now add a lot of debug logs in your actor, which will help you when something goes wrong and turn them on or off with a+simple `INPUT` change, or by setting an environment variable.++The punch line? Use `Apify.utils.log` instead of `console.log` now and thank us later when something goes wrong!++#### Using a router to structure your crawling++At first, it might seem more readable using just a simple `if / else` statement to select different logic based on the crawled pages, but trust me, it+becomes far less impressive when working with more than 2 different pages and it definitely starts to fall apart when the logic to handle each page+spans tens or hundreds of lines of code.++It's a good practice in any programming to split your logic into bite sized chunks that are easy to read and reason about. Scrolling through a+thousand line long `handlePageFunction()` where everything interacts with everything and variables can be used everywhere is not a beautiful thing to+do and a pain to debug. That's why we prefer the separation of routes into a special file and with large routes, we would even suggest having one file+per route.++> TO BE CONTINUED with details on `PuppeteerCrawler` and other features...diff --git a/website/versioned_docs/version-1.1.0/guides/quick_start.md b/website/versioned_docs/version-1.1.0/guides/quick_start.mdnew file mode 100644index 000000000..d35f63f5b--- /dev/null+++ b/website/versioned_docs/version-1.1.0/guides/quick_start.md@@ -0,0 +1,110 @@+---+id: version-1.1.0-quick-start+title: Quick Start+original_id: quick-start+---++This short tutorial will set you up to start using Apify SDK in a minute or two.+If you want to learn more, proceed to the [Getting Started](../guides/getting-started)+tutorial that will take you step by step through creating your first scraper.++## Local stand-alone usage+Apify SDK requires [Node.js](https://nodejs.org/en/) 10.17 or later, with the exception of Node.js 11.+Add Apify SDK to any Node.js project by running:++```bash+npm install apify playwright+```++> Neither `playwright` nor `puppeteer` are bundled with the SDK to reduce install size and allow greater+> flexibility. That's why we install it with NPM. You can choose one, both, or neither.++Run the following example to perform a recursive crawl of a website using Playwright. For more examples showcasing various features of the Apify SDK,+[see the Examples section of the documentation](../examples/crawl-multiple-urls).++```javascript+const Apify = require('apify');++// Apify.main is a helper function, you don't need to use it.+Apify.main(async () => {+ const requestQueue = await Apify.openRequestQueue();+ // Choose the first URL to open.+ await requestQueue.addRequest({ url: 'https://www.iana.org/' });++ const crawler = new Apify.PlaywrightCrawler({+ requestQueue,+ handlePageFunction: async ({ request, page }) => {+ // Extract HTML title of the page.+ const title = await page.title();+ console.log(`Title of ${request.url}: ${title}`);++ // Add URLs that match the provided pattern.+ await Apify.utils.enqueueLinks({+ page,+ requestQueue,+ pseudoUrls: ['https://www.iana.org/[.*]'],+ });+ },+ });++ await crawler.run();+});+```++> To read more about what pseudo-URL is, check the [getting-started](getting_started#introduction-to-pseudo-urls).++When you run the example, you should see Apify SDK automating a Chrome browser.++++By default, Apify SDK stores data to `./apify_storage` in the current working directory. You can override this behavior by setting either the+`APIFY_LOCAL_STORAGE_DIR` or `APIFY_TOKEN` environment variable. For details, see [Environment variables](../guides/environment-variables), [Request storage](../guides/request-storage) and [Result storage](../guides/result-storage).++## Local usage with Apify command-line interface (CLI)++To avoid the need to set the environment variables manually, to create a boilerplate of your project, and to enable pushing and running your code on+the [Apify platform](../guides/apify-platform), you can use the [Apify command-line interface (CLI)](https://github.com/apify/apify-cli) tool.++Install the CLI by running:++```bash+npm -g install apify-cli+```++Now create a boilerplate of your new web crawling project by running:++```bash+apify create my-hello-world+```++The CLI will prompt you to select a project boilerplate template - just pick "Hello world". The tool will create a directory called `my-hello-world`+with a Node.js project files. You can run the project as follows:++```bash+cd my-hello-world+apify run+```++By default, the crawling data will be stored in a local directory at `./apify_storage`. For example, the input JSON file for the actor is expected to+be in the default key-value store in `./apify_storage/key_value_stores/default/INPUT.json`.++Now you can easily deploy your code to the Apify platform by running:++```bash+apify login+```++```bash+apify push+```++Your script will be uploaded to the Apify platform and built there so that it can be run. For more information, view the+[Apify Actor](https://docs.apify.com/cli) documentation.++## Usage on the Apify platform++You can also develop your web scraping project in an online code editor directly on the [Apify platform](../guides/apify-platform).+You'll need to have an Apify Account. Go to [Actors](https://my.apify.com/actors), page in the app, click <i>Create new</i>+and then go to the <i>Source</i> tab and start writing your code or paste one of the examples from the Examples section.++For more information, view the [Apify actors quick start guide](https://docs.apify.com/actor/quick-start).diff --git a/website/versioned_docs/version-1.1.0/guides/typescript_actor.md b/website/versioned_docs/version-1.1.0/guides/typescript_actor.mdnew file mode 100644index 000000000..b263a79f2--- /dev/null+++ b/website/versioned_docs/version-1.1.0/guides/typescript_actor.md@@ -0,0 +1,133 @@+---+id: version-1.1.0-type-script-actor+title: TypeScript Actors+original_id: type-script-actor+---++Apify SDK supports TypeScript by covering public APIs with type declarations. This+allows writing code with auto-completion for TypeScript and JavaScript code alike.+Besides that, actors written in TypeScript can take advantage of compile-time+type-checking and avoid many coding mistakes, while providing documentation for+functions, parameters and return values.++Setting up a TypeScript project+=============================++To use TypeScript in your actors, you'll need the following prerequisites.++1. TypeScript compiler `tsc` installed somewhere:++ ```shell script+ npm install --dev typescript+ ```++ TypeScript can be a development dependency in your project, as shown above. There's no+ need to pollute your production environment or your system's global repository+ with TypeScript.++2. A build script invoking `tsc` and a correctly specified `main` entry point defined+ in your `package.json`:++ ```json+ {+ "scripts": {+ "build": "tsc -p tsconfig.json"+ },+ "main": "build/main.js"+ }+ ```++3. Type declarations for NodeJS, so you can take advantage of type-checking in all the features you'll use:++ ```shell script+ npm install --dev @types/node+ ```++4. TypeScript configuration file allowing `tsc` to understand your project layout and+ the features used in your project:++ ```json+ {+ "compilerOptions": {+ "target": "es2019",+ "module": "commonjs",+ "moduleResolution": "node",+ "strict": true,+ "noImplicitAny": false,+ "strictNullChecks": false,+ "lib": [+ "DOM",+ "DOM.Iterable",+ "ES2015",+ "ES2016",+ "ES2018",+ "ES2019.Object",+ "ES2018.AsyncIterable",+ "ES2020.String",+ "ES2019.Array"+ ],+ "rootDir": "src/",+ "outDir": "build/"+ },+ "include": [+ "src/"+ ]+ }+ ```++ Place the content above inside a `tsconfig.json` in your root folder.++ Also, if you are a VSCode user that is using JavaScript, create a `jsconfig.json` with the same content, adding `"checkJs": true` to `"compilerOptions"`, so you can enjoy using the types in your `.js` source files.++Auto-completion+==============++IDE auto-completion should work in most places. That's true even if you are writting+actors in pure JavaScript. For time constraints, we left out the amendment of an+internal API for the time being, and these need to be added as the SDK developers write+new and enhance old code.++SDK Documentation+=================++SDK documentation has grown a lot. There is a new API Reference section **Type definitions**+that holds documentation for all constructible types, function parameters and+return types, in the Apify SDK.++Caveats+========++As of version 1.0+, the generated typings, due to JSDoc limitations, have some properties+and parameters annotated with `any` type, therefore the settings `noImplicitAny` and `strictNullChecks`, set to `true`, may not be advised. You may try enabling them, but it might hinder development because of the need for typecasts to be able to compile, your mileage may vary.++Besides the _implicit any_ errors that might occur in the code when writing in TypeScript, the+current typings doesn't offer generics that make outputs type-safe, so you need to declare your+types, as such:++```typescript+interface MySchema {+ expectedParam1?: string;+ expectedParam2?: number;+}++const input: MySchema = (await Apify.getInput()) as any; // getInput returns Promise<Object<string, *>|string|Buffer|null> here++if (!input?.expectedParam1) { // input is MySchema now and you can check in a type-safe way+ throw new Error('Missing expectedParam1');+}+```++There are also other places where you need to explicitly provide your interface / type, like in Dataset iterators (`map`, `reduce`, `forEach`):++```typescript+interface ExpectedShape {+ id: string;+ someFields: Fields[];+}++const dataset = await Apify.openDataset();+await dataset.forEach((item: ExpectedShape) => {+ // deal with item.id / item.someFields+ // otherwise item is "any"+})+```diff --git a/website/versioned_docs/version-1.1.0/typedefs/PlaywrightCrawlerOptions.md b/website/versioned_docs/version-1.1.0/typedefs/PlaywrightCrawlerOptions.mdnew file mode 100644index 000000000..067f74081--- /dev/null+++ b/website/versioned_docs/version-1.1.0/typedefs/PlaywrightCrawlerOptions.md@@ -0,0 +1,242 @@+---+id: version-1.1.0-playwright-crawler-options+title: PlaywrightCrawlerOptions+original_id: playwright-crawler-options+---++<a name="playwrightcrawleroptions"></a>++## Properties++### `handlePageFunction`++**Type**: [`PlaywrightHandlePageFunction`](../typedefs/playwright-handle-page-function)++Function that is called to process each request. It is passed an object with the following fields:++```+{+ request: Request,+ response: Response,+ page: Page,+ session: Session,+ browserController: BrowserController,+ proxyInfo: ProxyInfo,+ crawler: PlaywrightCrawler,+}+```++`request` is an instance of the [`Request`](../api/request) object with details about the URL to open, HTTP method etc. `page` is an instance of the+`Playwright` [`Page`](https://playwright.dev/docs/api/class-page) `browserController` is an instance of the+[`BrowserController`](https://github.com/apify/browser-pool#browsercontroller), `response` is an instance of the `Playwright`+[`Response`](https://playwright.dev/docs/api/class-response), which is the main resource response as returned by `page.goto(request.url)`. The+function must return a promise, which is then awaited by the crawler.++If the function throws an exception, the crawler will try to re-crawl the request later, up to `option.maxRequestRetries` times. If all the retries+fail, the crawler calls the function provided to the `handleFailedRequestFunction` parameter. To make this work, you should **always** let your+function throw exceptions rather than catch them. The exceptions are logged to the request using the+[`Request.pushErrorMessage()`](../api/request#pusherrormessage) function.++---++### `navigationTimeoutSecs`++**Type**: `number` <code> = 60</code>++Timeout in which page navigation needs to finish, in seconds.++---++### `handleFailedRequestFunction`++**Type**: [`HandleFailedRequest`](../typedefs/handle-failed-request)++A function to handle requests that failed more than `option.maxRequestRetries` times.++The function receives the following object as an argument:++```+{+ request: Request,+ response: Response,+ page: Page,+ session: Session,+ browserController: BrowserController,+ proxyInfo: ProxyInfo,+ crawler: PlaywrightCrawler,+}+```++Where the [`Request`](../api/request) instance corresponds to the failed request, and the `Error` instance represents the last error thrown during+processing of the request.++---++### `preNavigationHooks`++**Type**: [`Array<PlaywrightHook>`](../typedefs/playwright-hook)++Async functions that are sequentially evaluated before the navigation. Good for setting additional cookies or browser properties before navigation.+The function accepts two parameters, `crawlingContext` and `gotoOptions`, which are passed to the `page.goto()` function the crawler calls to+navigate. Example:++```+preNavigationHooks: [+ async (crawlingContext, gotoOptions) => {+ await page.evaluate((attr) => { window.foo = attr; }, 'bar');+ }+]+```++---++### `postNavigationHooks`++**Type**: [`Array<PlaywrightHook>`](../typedefs/playwright-hook)++Async functions that are sequentially evaluated after the navigation. Good for checking if the navigation was successful. The function accepts+`crawlingContext` as an only parameter. Example:++```+postNavigationHooks: [+ async (crawlingContext) => {+ const { page } = crawlingContext;+ if (hasCaptcha(page)) {+ await solveCaptcha (page);+ }+ };+]+```++---++### `launchContext`++**Type**: [`PlaywrightLaunchContext`](../typedefs/playwright-launch-context)++The same options as used by [`Apify.launchPlaywright()`](../api/apify#launchplaywright).++---++### `handlePageTimeoutSecs`++**Type**: `number` <code> = 60</code>++Timeout in which the function passed as `handlePageFunction` needs to finish, in seconds.++---++### `browserPoolOptions`++**Type**: `BrowserPoolOptions`++Custom options passed to the underlying [`BrowserPool`](https://github.com/apify/browser-pool#BrowserPool) constructor. You can tweak those to+fine-tune browser management.++---++### `persistCookiesPerSession`++**Type**: `boolean` <code> = true</code>++Automatically saves cookies to Session. Works only if Session Pool is used.++---++### `proxyConfiguration`++**Type**: [`ProxyConfiguration`](../api/proxy-configuration)++If set, `PlaywrightCrawler` will be configured for all connections to use [Apify Proxy](https://my.apify.com/proxy) or your own Proxy URLs provided+and rotated according to the configuration. For more information, see the [documentation](https://docs.apify.com/proxy).++---++### `requestList`++**Type**: [`RequestList`](../api/request-list)++Static list of URLs to be processed. Either `requestList` or `requestQueue` option must be provided (or both).++---++### `requestQueue`++**Type**: [`RequestQueue`](../api/request-queue)++Dynamic queue of URLs to be processed. This is useful for recursive crawling of websites. Either `requestList` or `requestQueue` option must be+provided (or both).++---++### `handleRequestTimeoutSecs`++**Type**: `number` <code> = 60</code>++Timeout in which the function passed as `handleRequestFunction` needs to finish, in seconds.++---++### `maxRequestRetries`++**Type**: `number` <code> = 3</code>++Indicates how many times the request is retried if+[`PlaywrightCrawlerOptions.handlePageFunction`](../typedefs/playwright-crawler-options#handlepagefunction) fails.++---++### `maxRequestsPerCrawl`++**Type**: `number`++Maximum number of pages that the crawler will open. The crawl will stop when this limit is reached. Always set this value in order to prevent infinite+loops in misconfigured crawlers. Note that in cases of parallel crawling, the actual number of pages visited might be slightly higher than this value.++---++### `autoscaledPoolOptions`++**Type**: [`AutoscaledPoolOptions`](../typedefs/autoscaled-pool-options)++Custom options passed to the underlying [`AutoscaledPool`](../api/autoscaled-pool) constructor. Note that the `runTaskFunction` and+`isTaskReadyFunction` options are provided by `BasicCrawler` and cannot be overridden. However, you can provide a custom implementation of+`isFinishedFunction`.++---++### `minConcurrency`++**Type**: `number` <code> = 1</code>++Sets the minimum concurrency (parallelism) for the crawl. Shortcut to the corresponding [`AutoscaledPool`](../api/autoscaled-pool) option.++_WARNING:_ If you set this value too high with respect to the available system memory and CPU, your crawler will run extremely slow or crash. If+you're not sure, just keep the default value and the concurrency will scale up automatically.++---++### `maxConcurrency`++**Type**: `number` <code> = 1000</code>++Sets the maximum concurrency (parallelism) for the crawl. Shortcut to the corresponding [`AutoscaledPool`](../api/autoscaled-pool) option.++---++### `useSessionPool`++**Type**: `boolean` <code> = true</code>++Playwright crawler will initialize the [`SessionPool`](../api/session-pool) with the corresponding `sessionPoolOptions`. The session instance will be+than available in the `handleRequestFunction`.++---++### `sessionPoolOptions`++**Type**: [`SessionPoolOptions`](../typedefs/session-pool-options)++The configuration options for [`SessionPool`](../api/session-pool) to use.++---diff --git a/website/versioned_docs/version-1.1.0/typedefs/PlaywrightLaunchContext.md b/website/versioned_docs/version-1.1.0/typedefs/PlaywrightLaunchContext.mdnew file mode 100644index 000000000..3fb270c1d--- /dev/null+++ b/website/versioned_docs/version-1.1.0/typedefs/PlaywrightLaunchContext.md@@ -0,0 +1,65 @@+---+id: version-1.1.0-playwright-launch-context+title: PlaywrightLaunchContext+original_id: playwright-launch-context+---++<a name="playwrightlaunchcontext"></a>++Apify extends the launch options of Playwright. You can use any of the Playwright compatible+[`LaunchOptions`](https://playwright.dev/docs/api/class-browsertype#browsertypelaunchoptions) options by providing the `launchOptions` property.++**Example:**++```js+// launch a headless Chrome (not Chromium)+const launchContext = {+ // Apify helpers+ useChrome: true,+ proxyUrl: 'http://user:[email protected]'+ // Native Playwright options+ launchOptions: {+ headless: true,+ args: ['--some-flag'],+ }+}+```++## Properties++### `launchOptions`++**Type**: `LaunchOptions`++`browserType.launch` [options](https://playwright.dev/docs/api/class-browsertype?_highlight=launch#browsertypelaunchoptions)++---++### `proxyUrl`++**Type**: `string`++URL to a HTTP proxy server. It must define the port number, and it may also contain proxy username and password.++Example: `http://bob:[email protected]:1234`.++---++### `useChrome`++**Type**: `boolean` <code> = false</code>++If `true` and `executablePath` is not set, Playwright will launch full Google Chrome browser available on the machine rather than the bundled+Chromium. The path to Chrome executable is taken from the `APIFY_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 `false`.++---++### `launcher`++**Type**: `*`++By default this function uses `require("playwright").chromium`. If you want to use a different browser you can pass it by this property as e.g.+`require("playwright").firefox`++---diff --git a/website/versioned_docs/version-1.1.0/typedefs/PuppeteerCrawlerOptions.md b/website/versioned_docs/version-1.1.0/typedefs/PuppeteerCrawlerOptions.mdnew file mode 100644index 000000000..c9c0561a0--- /dev/null+++ b/website/versioned_docs/version-1.1.0/typedefs/PuppeteerCrawlerOptions.md@@ -0,0 +1,244 @@+---+id: version-1.1.0-puppeteer-crawler-options+title: PuppeteerCrawlerOptions+original_id: puppeteer-crawler-options+---++<a name="puppeteercrawleroptions"></a>++## Properties++### `handlePageFunction`++**Type**: [`PuppeteerHandlePage`](../typedefs/puppeteer-handle-page)++Function that is called to process each request. It is passed an object with the following fields:++```+{+ request: Request,+ response: Response,+ page: Page,+ session: Session,+ browserController: BrowserController,+ proxyInfo: ProxyInfo,+ crawler: PuppeteerCrawler,+}+```++`request` is an instance of the [`Request`](../api/request) object with details about the URL to open, HTTP method etc. `page` is an instance of the+`Puppeteer` [`Page`](https://pptr.dev/#?product=Puppeteer&show=api-class-page) `browserPool` is an instance of the+[`BrowserPool`](https://github.com/apify/browser-pool#BrowserPool), `browserController` is an instance of the+[`BrowserController`](https://github.com/apify/browser-pool#browsercontroller), `response` is an instance of the `Puppeteer`+[`Response`](https://pptr.dev/#?product=Puppeteer&show=api-class-response), which is the main resource response as returned by+`page.goto(request.url)`. The function must return a promise, which is then awaited by the crawler.++If the function throws an exception, the crawler will try to re-crawl the request later, up to `option.maxRequestRetries` times. If all the retries+fail, the crawler calls the function provided to the `handleFailedRequestFunction` parameter. To make this work, you should **always** let your+function throw exceptions rather than catch them. The exceptions are logged to the request using the+[`Request.pushErrorMessage()`](../api/request#pusherrormessage) function.++---++### `navigationTimeoutSecs`++**Type**: `number` <code> = 60</code>++Timeout in which page navigation needs to finish, in seconds.++---++### `handleFailedRequestFunction`++**Type**: [`HandleFailedRequest`](../typedefs/handle-failed-request)++A function to handle requests that failed more than `option.maxRequestRetries` times.++The function receives the following object as an argument:++```+{+ request: Request,+ response: Response,+ page: Page,+ session: Session,+ browserController: BrowserController,+ proxyInfo: ProxyInfo,+ crawler: PuppeteerCrawler,+}+```++Where the [`Request`](../api/request) instance corresponds to the failed request, and the `Error` instance represents the last error thrown during+processing of the request.++---++### `launchContext`++**Type**: [`PuppeteerLaunchContext`](../typedefs/puppeteer-launch-context)++Options used by [`Apify.launchPuppeteer()`](../api/apify#launchpuppeteer) to start new Puppeteer instances.++---++### `handlePageTimeoutSecs`++**Type**: `number` <code> = 60</code>++Timeout in which the function passed as `handlePageFunction` needs to finish, in seconds.++---++### `browserPoolOptions`++**Type**: `BrowserPoolOptions`++Custom options passed to the underlying [`BrowserPool`](https://github.com/apify/browser-pool#BrowserPool) constructor. You can tweak those to+fine-tune browser management.++---++### `persistCookiesPerSession`++**Type**: `boolean` <code> = true</code>++Automatically saves cookies to Session. Works only if Session Pool is used.++---++### `proxyConfiguration`++**Type**: [`ProxyConfiguration`](../api/proxy-configuration)++If set, `PuppeteerCrawler` will be configured for all connections to use [Apify Proxy](https://my.apify.com/proxy) or your own Proxy URLs provided and+rotated according to the configuration. For more information, see the [documentation](https://docs.apify.com/proxy).++---++### `preNavigationHooks`++**Type**: [`Array<PuppeteerHook>`](../typedefs/puppeteer-hook)++Async functions that are sequentially evaluated before the navigation. Good for setting additional cookies or browser properties before navigation.+The function accepts two parameters, `crawlingContext` and `gotoOptions`, which are passed to the `page.goto()` function the crawler calls to+navigate. Example:++```+preNavigationHooks: [+ async (crawlingContext, gotoOptions) => {+ const { page } = crawlingContext;+ await page.evaluate((attr) => { window.foo = attr; }, 'bar');+ }+]+```++---++### `postNavigationHooks`++**Type**: [`Array<PuppeteerHook>`](../typedefs/puppeteer-hook)++Async functions that are sequentially evaluated after the navigation. Good for checking if the navigation was successful. The function accepts+`crawlingContext` as an only parameter. Example:++```+postNavigationHooks: [+ async (crawlingContext) => {+ const { page } = crawlingContext;+ if (hasCaptcha(page)) {+ await solveCaptcha (page);+ }+ };+]+```++---++### `requestList`++**Type**: [`RequestList`](../api/request-list)++Static list of URLs to be processed. Either `requestList` or `requestQueue` option must be provided (or both).++---++### `requestQueue`++**Type**: [`RequestQueue`](../api/request-queue)++Dynamic queue of URLs to be processed. This is useful for recursive crawling of websites. Either `requestList` or `requestQueue` option must be+provided (or both).++---++### `handleRequestTimeoutSecs`++**Type**: `number` <code> = 60</code>++Timeout in which the function passed as `handleRequestFunction` needs to finish, in seconds.++---++### `maxRequestRetries`++**Type**: `number` <code> = 3</code>++Indicates how many times the request is retried if+[`PuppeteerCrawlerOptions.handlePageFunction`](../typedefs/puppeteer-crawler-options#handlepagefunction) fails.++---++### `maxRequestsPerCrawl`++**Type**: `number`++Maximum number of pages that the crawler will open. The crawl will stop when this limit is reached. Always set this value in order to prevent infinite+loops in misconfigured crawlers. Note that in cases of parallel crawling, the actual number of pages visited might be slightly higher than this value.++---++### `autoscaledPoolOptions`++**Type**: [`AutoscaledPoolOptions`](../typedefs/autoscaled-pool-options)++Custom options passed to the underlying [`AutoscaledPool`](../api/autoscaled-pool) constructor. Note that the `runTaskFunction` and+`isTaskReadyFunction` options are provided by `BasicCrawler` and cannot be overridden. However, you can provide a custom implementation of+`isFinishedFunction`.++---++### `minConcurrency`++**Type**: `number` <code> = 1</code>++Sets the minimum concurrency (parallelism) for the crawl. Shortcut to the corresponding [`AutoscaledPool`](../api/autoscaled-pool) option.++_WARNING:_ If you set this value too high with respect to the available system memory and CPU, your crawler will run extremely slow or crash. If+you're not sure, just keep the default value and the concurrency will scale up automatically.++---++### `maxConcurrency`++**Type**: `number` <code> = 1000</code>++Sets the maximum concurrency (parallelism) for the crawl. Shortcut to the corresponding [`AutoscaledPool`](../api/autoscaled-pool) option.++---++### `useSessionPool`++**Type**: `boolean` <code> = true</code>++Puppeteer crawler will initialize the [`SessionPool`](../api/session-pool) with the corresponding `sessionPoolOptions`. The session instance will be+than available in the `handleRequestFunction`.++---++### `sessionPoolOptions`++**Type**: [`SessionPoolOptions`](../typedefs/session-pool-options)++The configuration options for [`SessionPool`](../api/session-pool) to use.++---diff --git a/website/versioned_docs/version-1.1.0/typedefs/PuppeteerLaunchContext.md b/website/versioned_docs/version-1.1.0/typedefs/PuppeteerLaunchContext.mdnew file mode 100644index 000000000..23ea3d08b--- /dev/null+++ b/website/versioned_docs/version-1.1.0/typedefs/PuppeteerLaunchContext.md@@ -0,0 +1,93 @@+---+id: version-1.1.0-puppeteer-launch-context+title: PuppeteerLaunchContext+original_id: puppeteer-launch-context+---++<a name="puppeteerlaunchcontext"></a>++Apify extends the launch options of Puppeteer. You can use any of the Puppeteer compatible+[`LaunchOptions`](https://pptr.dev/#?product=Puppeteer&show=api-puppeteerlaunchoptions) options by providing the `launchOptions` property.++**Example:**++```js+// launch a headless Chrome (not Chromium)+const launchContext = {+ // Apify helpers+ useChrome: true,+ proxyUrl: 'http://user:[email protected]'+ // Native Puppeteer options+ launchOptions: {+ headless: true,+ args: ['--some-flag'],+ }+}+```++## Properties++### `launchOptions`++**Type**: `LaunchOptions`++`puppeteer.launch` [options](https://pptr.dev/#?product=Puppeteer&version=v5.5.0&show=api-puppeteerlaunchoptions)++---++### `proxyUrl`++**Type**: `string`++URL to a HTTP proxy server. It must define the port number, and it may also contain proxy username and password.++Example: `http://bob:[email protected]:1234`.++---++### `userAgent`++**Type**: `string`++The `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.++---++### `useChrome`++**Type**: `boolean` <code> = false</code>++If `true` and `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 `APIFY_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 `false`.++---++### `launcher`++**Type**: `*`++Already required module (`Object`). This enables usage of various Puppeteer wrappers such as `puppeteer-extra`.++Take caution, because it can cause all kinds of unexpected errors and weird behavior. Apify SDK is not tested with any other library besides+`puppeteer` itself.++---++### `stealth`++**Type**: `boolean`++This setting hides most of the known properties that identify headless Chrome and makes it nearly undetectable. It is recommended to use it together+with the `useChrome` set to `true`.++---++### `stealthOptions`++**Type**: [`StealthOptions`](../typedefs/stealth-options)++Using this configuration, you can disable some of the hiding tricks. For these settings to take effect `stealth` must be set to true++---diff --git a/website/versioned_docs/version-1.1.0/typedefs/SessionPoolOptions.md b/website/versioned_docs/version-1.1.0/typedefs/SessionPoolOptions.mdnew file mode 100644index 000000000..0dbccc1c9--- /dev/null+++ b/website/versioned_docs/version-1.1.0/typedefs/SessionPoolOptions.md@@ -0,0 +1,50 @@+---+id: version-1.1.0-session-pool-options+title: SessionPoolOptions+original_id: session-pool-options+---++<a name="sessionpooloptions"></a>++## Properties++### `maxPoolSize`++**Type**: `number` <code> = 1000</code>++Maximum size of the pool. Indicates how many sessions are rotated.++---++### `sessionOptions`++**Type**: [`SessionOptions`](../typedefs/session-options)++The configuration options for [`Session`](../api/session) instances.++---++### `persistStateKeyValueStoreId`++**Type**: `string`++Name or Id of `KeyValueStore` where is the `SessionPool` state stored.++---++### `persistStateKey`++**Type**: `string` <code> = "\"SESSION_POOL_STATE\""</code>++Session pool persists it's state under this key in Key value store.++---++### `createSessionFunction`++**Type**: [`CreateSession`](../typedefs/create-session)++Custom function that should return `Session` instance. Any error thrown from this function will terminate the process. Function receives `SessionPool`+instance as a parameter++---diff --git a/website/versions.json b/website/versions.jsonindex dece73bfd..58f1f9589 100644--- a/website/versions.json+++ b/website/versions.json@@ -1,4 +1,5 @@[+ "1.1.0","1.0.2","1.0.1","1.0.0",