/**
 * Installing the Aseprite side.
 *
 * Aseprite loads extensions from a per-user config directory whose location
 * differs on every platform and moves between the store and standalone builds.
 * Getting this wrong is the single most common reason a setup "does nothing",
 * so the search order is explicit and `doctor` reports what it found.
 */
/** Candidate Aseprite user-config directories, most likely first. */
export declare function asepriteConfigCandidates(): string[];
export declare function findAsepriteConfigDir(): string | null;
/**
 * Where an Aseprite executable usually lives when `ASEPRITE_PATH` is not set:
 * the standalone and Steam install locations, then `aseprite` on PATH.
 */
export declare function asepriteBinaryCandidates(env?: NodeJS.ProcessEnv): string[];
/**
 * The Aseprite executable headless mode will run, or null when there is none.
 * An explicit `ASEPRITE_PATH` that points nowhere is null, not a cue to try
 * the other locations: running a different Aseprite than the one the user
 * named would be a silent substitution they have no way to notice.
 */
export declare function findAsepriteBinary(env?: NodeJS.ProcessEnv): string | null;
export interface InstallExtensionOptions {
    dryRun?: boolean;
    /** Override the Aseprite config directory. */
    configDir?: string | undefined;
}
export interface InstallExtensionResult {
    target: string;
    files: string[];
}
export declare function installExtension(opts?: InstallExtensionOptions): InstallExtensionResult;