/**
 * Compute, for each line of a TS/JS source, whether the line begins inside
 * a template-literal body (i.e. between an unclosed backtick and its
 * matching close).
 *
 * Used by rules like `prefer-const` and `pickier/no-unused-vars` to skip
 * generated code embedded in template strings — declarations and function
 * bodies inside a `\`<script>...\`` blob aren't real top-level code, and
 * applying lint rules to them produces false positives that fixers will
 * happily turn into broken runtime code.
 *
 * Tracks: single-quoted strings, double-quoted strings, template-literal
 * bodies + their `${}` expressions (with brace depth), regex literals
 * (with character-class awareness), line and block comments.
 *
 * Regex-vs-division disambiguation uses the previous "significant"
 * character on the logical statement: `/` after operators / punctuation
 * starts a regex; `/` after an identifier or closing bracket is division.
 */
export declare function computeLineStartsInTemplate(text: string): boolean[];
/**
 * On a single line, return [start, end] ranges of characters that fall
 * inside a backtick-bounded template literal. If a backtick opens but
 * doesn't close on this line, the range extends to the line's end (it's
 * the first line of a multi-line template).
 *
 * Used by per-line fixers to refuse to rewrite identifiers that fall
 * inside an embedded code blob whose other usages live in the same
 * template string and aren't visible to the syntactic rename.
 */
export declare function backtickRangesOnLine(line: string): Array<[number, number]>;