import { EngineHandle, VfsBackend } from '../core/types';
export interface TauriFsOptions {
    /** Subdirectory under the chosen base dir where the TDS lives. e.g. "texmf". */
    texmfRoot: string;
    /**
     * Tauri BaseDirectory enum value. We accept it as a number to avoid a
     * hard dependency on @tauri-apps/api types here. Prefer importing
     * `BaseDirectory` from @tauri-apps/plugin-fs; for reference, Tauri 2
     * values are: Resource = 11, AppConfig = 13, AppData = 14,
     * AppLocalData = 15.
     */
    baseDir: number;
}
/**
 * Create a TauriFS backend. Imports @tauri-apps/plugin-fs dynamically so this
 * module doesn't pull it in for non-Tauri consumers.
 */
export declare function createTauriFs(opts: TauriFsOptions): Promise<VfsBackend>;
/**
 * Detect whether the current runtime is a Tauri app. Cheap and safe to
 * call from anywhere (returns false in Node, browsers, web workers).
 */
export declare function isTauri(): boolean;
/**
 * Convenience: create an engine with TauriFS prepended to its backend list.
 *
 * Use this when the consumer wants the engine to read TDS files straight
 * from the bundled Tauri resources. The TauriFs backend is consulted first
 * (highest priority), so any file present locally wins over CDN fallback.
 *
 * The actual engine is constructed by the caller-supplied factory, which
 * receives the prepared backend chain. In practice the factory is just
 * `createEngine` from this package.
 */
export declare function withTauriFs(factory: (vfs: VfsBackend[]) => Promise<EngineHandle>, opts: TauriFsOptions & {
    extraBackends?: VfsBackend[];
}): Promise<EngineHandle>;
//# sourceMappingURL=taurifs.d.ts.map