import type { INearestId } from './i-nearest-id.js';
/**
 * Nearest-id "did you mean" over an arbitrary id set — the closest ids to
 * `query`, nearest first.
 *
 * The command suggester already had a Levenshtein and a fuzzy ranker, but both
 * were shaped around a command CATALOG (command paths, aliases, descriptions).
 * A stale `nge.angular-renderer` in a doc needs the same help against a flat
 * list of template ids, so the distance function is shared and every caller
 * consumes it — a second implementation would drift, and then two surfaces
 * would disagree about what "close" means.
 *
 * A suggestion is only offered when it is actually close. Printing the
 * alphabetically-first id next to every typo trains people to ignore the line.
 * The cutoff scales with the query's length — one edit is a lot in `foo` and
 * very little in `nge.angular-renderer` — and is capped so a long id cannot
 * drag in something unrelated. Ties break lexically so the output is stable
 * across runs, which matters when it lands in a committed diff.
 *
 * Lives in `core` (round 13) next to {@link levenshtein}; `@shrkcrft/inspector`
 * re-exports both unchanged.
 */
export declare function nearestIds(query: string, candidates: readonly string[], limit?: number): readonly INearestId[];
//# sourceMappingURL=nearest-ids.d.ts.map