/*!
 * Copyright (c) Microsoft Corporation and contributors. All rights reserved.
 * Licensed under the MIT License.
 */
import type { ExportDeclaration, ExportedDeclarations, SourceFile } from "ts-morph";
interface ExportRecord {
    name: string;
    isTypeOnly: boolean;
}
interface ExportRecords {
    public: ExportRecord[];
    beta: ExportRecord[];
    alpha: ExportRecord[];
    internal: ExportRecord[];
    legacyPublic: ExportRecord[];
    legacyBeta: ExportRecord[];
    legacyAlpha: ExportRecord[];
    /**
     * Entries here represent exports with unrecognized tags.
     * These may be errors or just concerns depending on context.
     * ExportedDeclarations provides context for the origin of
     * such cases.
     */
    unknown: Map<string, {
        exportedDecl: ExportedDeclarations;
        exportDecl?: ExportDeclaration;
    }>;
}
/**
 * Given a source file, extracts all of the named exports and associated support levels.
 * Named exports without a recognized tag are placed in unknown array.
 */
export declare function getApiExports(sourceFile: SourceFile): ExportRecords;
/**
 * Searches given source file for the package documentation (first
 * `@packageDocumentation` tagged comment).
 *
 * @returns Found full text of the package documentation or empty string.
 *
 * @privateRemarks
 * If we find trouble with practical extraction, consider replicating api-extractor's logic at:
 * {@link https://github.com/microsoft/rushstack/blob/main/apps/api-extractor/src/aedoc/PackageDocComment.ts}
 *
 * Here a simplified approach is taken leveraging ts-morph's comment organization.
 */
export declare function getPackageDocumentationText(sourceFile: SourceFile): string;
export {};
//# sourceMappingURL=typescriptApi.d.ts.map