apify-sdk-patterns

# Apify SDK Patterns ## Overview Production patterns for both the `apify` SDK (building Actors) and `apify-client` (calling Actors remotely). Covers Crawlee crawler selection, data storage, proxy configuration, and typed client wrappers. ## Prerequisites - `apify-client` and/or `apify` + `crawlee` installed - `APIFY_TOKEN` configured - TypeScript recommended ## Pattern 1: Typed Client Singleton ```typescript // src/apify/client.ts import { ApifyClient } from 'apify-client'; let instance: ApifyClient | null = null; export function getApifyClient(): ApifyClient { if (!instance) { const token = process.env.APIFY_TOKEN; if (!token) throw new Error('APIFY_TOKEN is required'); instance = new ApifyClient({ token }); } return instance; } // Reset for testing export function resetClient(): void { instance = null; } ``` ## Pattern 2: Crawlee Crawler Selection Choose the right crawler for the job: ```typescript import { CheerioCrawler, PlaywrightCrawler, PuppeteerCrawler } from 'crawlee'; // CHEERIO — Fast, lightweight, no JavaScript rendering // Use for: static HTML, server-rendered pages, APIs const cheerioCrawler = new CheerioCrawler({ async requestHandler({ request, $, enqueueLinks }) { const title = $('title').text(); await Actor.pushData({ url: request.url, title }); await enqueueLinks({ strategy: 'same-domain' }); }, }); // PLAYWRIGHT — Full browser, all engines, modern API // Use for: SPAs, JavaScript-heavy pages, complex interac...