/**
 * Svelte usage walker. `svelte/compiler.parse` (lazily imported) yields one AST
 * whose Root holds the module/instance scripts (estree) *and* the template, so a
 * single iterative walk reaches every translate call — script-level and inside
 * markup expressions — with original-source offsets for accurate line numbers.
 *
 * On top of the estree handling (mirroring the TypeScript walker) it understands
 * the `<T key="…">` component, the markup form of a translation render-call.
 */
import type { ScanOptions, UsageScan } from './types.js';
export declare function scanSvelte(code: string, file: string, options?: ScanOptions): Promise<UsageScan>;