/**
 * The Web surface's own answers about names: which record a runtime type name
 * carries, which event type a DOM event name resolves to, which ValueType each
 * Look property accepts, and the small rosters and sentence builders the
 * analyzer reads beside them.
 *
 * D115 P4 R3a: every one of these is a total function over a name, or the table
 * one reads. None of them needs the analyzer's walk state, so they read as a
 * module rather than as 150 lines standing between the analyzer's imports and
 * its first collaborator.
 */
import { type Diagnostic, type DiagnosticFix, type Span } from "@velarscript/compiler";
import { type ValueType } from "@velarscript/compiler/extension";
export declare const routeContextIdentity = "@velarscript/web:velar/web#type:RouteContext";
export declare const removedJsxControlAttributes: Set<string>;
export declare const nativeDomEventNames: Set<string>;
export declare const htmlEventHandlerAttributes: Set<string>;
export declare const textualWebPrimitiveNames: Set<string>;
export declare const webEventTypeNames: ReadonlySet<string>;
export declare const webEventDeadFields: Set<string>;
export declare const diagnostic: (code: string, message: string, sourceSpan: Span, fix?: DiagnosticFix) => Diagnostic;
export declare const bindTargetGuidance: (directive: string) => string;
export declare const lookLength: ValueType;
export declare const LOOK_PROPERTY_TYPES: Map<string, ValueType>;
export declare function webTypeFields(name: string): ReadonlyMap<string, ValueType> | null;
export declare function webEventType(name: string): ValueType;
//# sourceMappingURL=web-types.d.ts.map