export interface NpmRegistryError extends Error {
    /** HTTP status code if the failure was at the response layer. */
    statusCode?: number;
    /** Network error code (ENOTFOUND, ETIMEDOUT, ECONNRESET, …). */
    code?: string;
}
/**
 * Fetch the `latest` dist-tag manifest for `pkg` from the public npm
 * registry. Returns the parsed JSON.
 *
 * Throws `NpmRegistryError` with a concrete `.message` describing the
 * actual failure (HTTP status, network error code, parse failure). The
 * caller should surface that string instead of replacing it with a
 * generic "registry unreachable" — that wording was the original bug.
 */
export declare function fetchLatestManifest(pkg: string, opts?: {
    registry?: string;
    timeoutMs?: number;
}): Promise<{
    version: string;
    [key: string]: unknown;
}>;
/**
 * Convenience wrapper: returns just the `latest` version string.
 */
export declare function fetchLatestVersion(pkg: string, opts?: {
    registry?: string;
    timeoutMs?: number;
}): Promise<string>;
//# sourceMappingURL=npm-registry.d.ts.map