/**
 * NOTE: DETECTION only — "is something by this name installed". Actually SPAWNING
 * it on Windows is a different problem with different rules, and lives in
 * core/spawn-target.ts (`resolveSpawnTarget`): CreateProcess cannot execute a
 * `.cmd`, npm ships an unusable extensionless sh script beside it, and the shim's
 * real target may be a native `.exe`. The two deliberately differ — but if you
 * change candidate ordering here, check whether that module needs the same change.
 * A detect-says-yes / spawn-says-no split is exactly the bug that cost a day.
 */
/**
 * Find an executable on PATH, returning the full path of the first match in
 * PATH order, or null when there is none. Never throws.
 *
 * - POSIX: match must be a regular file with execute permission.
 * - Windows (win32): candidates are `name + ext` for each PATHEXT entry plus
 *   the bare name when it already carries an extension; existing as a regular
 *   file is enough (execute bits are meaningless on Windows).
 *
 * Empty PATH segments are skipped rather than treated as the current directory.
 */
export declare function findExecutableOnPath(name: string, env?: Record<string, string | undefined>, platform?: NodeJS.Platform): Promise<string | null>;
/** Convenience wrapper: true when the binary is reachable on PATH. */
export declare function isExecutableOnPath(name: string): Promise<boolean>;
//# sourceMappingURL=detect.d.ts.map