/**
 * The source as the rules should see it: comments and template-literal bodies blanked to spaces,
 * everything else byte-identical — same length, same line breaks — so a match still reports the real
 * file's line and column.
 *
 * Ordinary quoted strings are deliberately LEFT ALONE: an import specifier lives in one, and blanking
 * those would blind every rule that exists.
 *
 * Why: the rules match text, so import-shaped text that isn't an import trips them. An inline Web
 * Worker's source in a template literal — the pattern a WebGL/WASM bulb needs — fires `URL_IMPORT`,
 * and that bulb can then never pass `typebulb check`. This is also the direction the resolver already
 * takes: its authoritative extraction is `es-module-lexer` (`packageService.extractImports`), which
 * has never seen those regions as imports, so blanking converges lint with it rather than drifting.
 *
 * A scanner, not a parser. Regex literals are recognized only in expression position (after `(`,
 * `,`, `=` and kin) — which covers where bulb code actually puts them (`split(/…/)`, `= /…/`) —
 * because an unrecognized regex is the one gap that can fail toward *less* text being linted: a
 * backtick inside one opens a phantom template that blanks real code up to the next backtick,
 * suppressing findings. A regex outside those positions (after `return`, say) keeps that hazard;
 * the other gap — a `}` inside a string inside `${…}` closing the interpolation early — fails the
 * safe way, more text linted, a surviving false positive.
 */
export declare function codeView(source: string): string;
//# sourceMappingURL=codeView.d.ts.map