import type { ParseResult } from "../types/index.js";
export type ParseTSJSFn = (content: string, lines: string[]) => ParseResult;
interface SFCBlock {
    /** 1-indexed line number where the block's content starts. */
    startLine: number;
    /** 1-indexed line number where the block's content ends. */
    endLine: number;
    content: string;
    lang?: string;
    setup?: boolean;
}
interface SFCBlocks {
    template: SFCBlock | null;
    /** The block we treat as canonical for symbol extraction (setup if both exist). */
    script: SFCBlock | null;
    /** The "other" script block when both `<script>` and `<script setup>` exist.
     *  We extract imports from BOTH so vue-extras setups (where one block holds
     *  metadata like defineOptions and the other holds reactive logic) keep all
     *  their dependency edges. Symbol extraction still only runs on `script`. */
    scriptSecondary: SFCBlock | null;
    style: SFCBlock | null;
    /** Custom top-level blocks like <i18n>, <route>, <docs> — captured
     *  for full-text search indexing. Vue ecosystem libraries
     *  (vite-plugin-pages, vue-i18n, unplugin-vue-router) put real
     *  configuration data in these blocks; ignoring them makes that
     *  data invisible to sverklo_search. Finding 8. */
    customBlocks: Array<SFCBlock & {
        tagName: string;
    }>;
}
export declare function parseSFCBlocks(content: string): SFCBlocks;
export declare function extractComponentRefs(template: string): string[];
export declare function parseVue(content: string, _lines: string[], parseTSJS: ParseTSJSFn): ParseResult;
export {};