/**
 * The Web extension's composition root. `compiler.ts` was one 1,136-line module;
 * D115 P4 R3e moved each `velar/*` surface's `ValueType` tables into its own
 * `modules/<surface>.ts` file and the editor prose into `documentation.ts`, and
 * left here what a composition root is: the published surface version, the
 * assembled module map, and the frozen extension literal every part of the
 * toolchain reads the Web target through.
 *
 * Where to look:
 *
 *  - `modules/types.ts`     the type vocabulary every surface table is written in
 *  - `modules/<surface>.ts` one file per `velar/*` surface, holding its tables and its entry
 *  - `module-roster.ts`     the ordered entry list this file assembles the map from
 *  - `documentation.ts`     the three editor-documentation tables
 */
import { type CompilerExtension, type ModuleInterface } from "@velarscript/compiler";
import { webModuleSource, webModuleSources, type VelarWebRuntimeConfig } from "./runtime.ts";
export declare const VELAR_WEB_API_VERSION = "0.14";
export { BROWSER_TEST_MODULE, BROWSER_TEST_SOURCE_SUFFIX } from "./browser-test.ts";
/**
 * The `velar/*` surfaces this capability publishes. One `modules/<surface>.ts`
 * file owns each entry's tables; `module-roster.ts` owns the order they are
 * assembled in, because a file this map is built from cannot import the map.
 */
export declare const webModuleInterfaces: ReadonlyMap<string, ModuleInterface>;
export declare const velarCompilerExtension: CompilerExtension;
export { webModuleSource, webModuleSources, type VelarWebRuntimeConfig };
export { velarProjectExtension, type VelarWebConfig } from "./project-config.ts";
//# sourceMappingURL=compiler.d.ts.map