/**
 * Static provider import map.
 *
 * Provider modules register themselves with the {@link ProviderRegistry} (via the
 * `@RegisterProvider` decorator) as a side effect of being imported, so the module must be
 * imported before the registry can construct the provider.
 *
 * These are written as **literal** dynamic-import specifiers — one arrow per provider —
 * rather than a single `import(variablePath)`. A literal specifier is statically
 * analyzable, so bundlers (Vite / Rollup / webpack) can code-split each provider into its
 * own lazily-loaded chunk and tree-shake the ones a consumer never configures, and Node's
 * native ESM resolver can resolve it. A runtime-built variable specifier satisfies neither
 * (Node ESM throws `ERR_MODULE_NOT_FOUND`; bundlers can't see the dependency), which
 * previously meant providers could silently fail to load and every event was dropped.
 *
 * Keyed by the provider's registry id (see `resolveProviderModule`): note `google` maps to
 * `google-analytics` and `crashlytics` maps to `firebase-crashlytics`.
 */
export type ProviderModuleLoader = () => Promise<unknown>;
export declare const PROVIDER_LOADERS: Readonly<Record<string, ProviderModuleLoader>>;
/** All known provider registry ids (analytics + error tracking). */
export declare const KNOWN_PROVIDER_IDS: readonly string[];