/**
 * Renderer-driven screenshot loop.
 *
 * Mirrors `PdfScreenshot.ts` in contract (same ScreenshotOptions, same
 * ScreenshotResult) but delegates the per-page rasterization to a pluggable
 * `PdfPageRenderer` (e.g. PuppeteerRenderer) instead of node-canvas.
 *
 * Kept as a separate file so the default node-canvas path stays untouched and
 * any regression here can't ripple back into existing consumers.
 */
import type { PdfDocument } from './PdfDocument.js';
import type { PdfPageRenderer } from '../types/renderer.types.js';
import type { ScreenshotOptions, ScreenshotResult } from '../types/screenshot.types.js';
import type { PdfDecomposerError, PdfDecomposerState } from '../types/decomposer.types.js';
/**
 * Run a screenshot pass through the provided renderer.
 *
 * Notes on behavior:
 * - The renderer's `initialize()` is assumed to have been called already by
 *   PdfDecomposer.initialize(). This function never calls initialize/dispose.
 * - Page release in `pdfDocument` still happens — even though the renderer
 *   may have its own pdf.js instance, the Node-side pdf.js owns text/image
 *   extraction state we still want to free.
 */
export declare function pdfScreenshotViaRenderer(pdfDocument: PdfDocument, renderer: PdfPageRenderer, options?: ScreenshotOptions, progressCallback?: (state: PdfDecomposerState) => void, errorCallback?: (error: PdfDecomposerError) => void): Promise<ScreenshotResult>;
//# sourceMappingURL=PdfScreenshotViaRenderer.d.ts.map