export interface ResolveCommandOptions {
    pathEnv?: string;
    pathext?: string;
    platform?: NodeJS.Platform;
    cacheTtlMs?: number;
    cacheFile?: string;
    disableCache?: boolean;
    now?: number;
}
/**
 * Synchronously check whether a command name resolves on the system PATH.
 *
 * Handles:
 * - Absolute paths and paths containing slashes (checked via `existsSync`)
 * - Windows executable/script extensions (`.COM`, `.EXE`, `.CMD`, `.BAT`, `.PS1`)
 * - Plain command names looked up across every `PATH` directory
 *
 * This is intentionally **synchronous** and side-effect free — no process is
 * spawned, so it completes in microseconds per call.
 */
export declare function isCommandOnPath(command: string): boolean;
/**
 * Resolve a command to the concrete file that will be launched.
 *
 * On Windows this checks the common executable/script shim extensions directly
 * instead of trusting PATHEXT alone. npm/nvm installations can expose only a
 * PowerShell shim (`.ps1`), and PATHEXT often omits `.PS1`.
 */
export declare function resolveCommandOnPath(command: string, options?: ResolveCommandOptions): string | null;
export declare function clearCommandResolutionCache(options?: {
    cacheFile?: string;
}): void;