/**
 * Resolves `resolve-peer-bump` fixes by consulting the npm registry.
 *
 * A `resolve-peer-bump` fix says "the installed peer X@v doesn't satisfy the
 * range that the currently installed version of the requiring dep D declares —
 * bump our declared range for D." To pick a concrete target range, we fetch
 * D's registry manifest and find the highest published version whose
 * `peerDependencies[X]` range accepts v. We then express our new declared
 * range using D's actual version numbers (not the peer's — that was the old
 * bug).
 *
 * If no published version of D accepts the installed peer, the fix is dropped
 * and the mismatch remains visible in the next deplint pass as a warning.
 */
import type { DeplintDiagnostic } from './types.ts';
/** Test-only. */
export declare function clearPeerBumpCache(): void;
/**
 * Mutates `diagnostics` in place: every `resolve-peer-bump` fix is replaced
 * with either a concrete `set-version` fix or removed entirely if no
 * published version of the requiring dep accepts the installed peer.
 */
export declare function resolvePeerBumpFixes(diagnostics: DeplintDiagnostic[]): Promise<void>;
//# sourceMappingURL=resolvePeerBumpFixes.d.ts.map