import type { VuecsInstallOptions, VuecsInstallOptionsInput } from './types';
/**
 * Register the Iconify icon collections authup's UI renders from
 * (Font Awesome 6 solid + brands). Call once at app bootstrap, before
 * the first `<VCIcon>` render.
 *
 * This registers BOTH collections in full: 1,902 icons, roughly 429 KB
 * gzip, where an app renders a few dozen. Prefer bundling only what is
 * rendered, which authup's own two apps do via `@nuxt/icon`'s standalone
 * vite plugin:
 *
 * ```ts
 * // vite.config.ts (or nuxt.config.ts under `vite.plugins`)
 * import { NuxtIconBundle } from '@nuxt/icon/vite';
 *
 * NuxtIconBundle({
 *     scan: {
 *         globInclude: [
 *             'src/**\/*.{vue,ts}',
 *             'node_modules/@authup/client-web-kit/dist/**\/*.mjs',
 *             'node_modules/@vuecs/icons-font-awesome/dist/*.mjs',
 *         ],
 *         globExclude: [],
 *     },
 * })
 * ```
 *
 * ```ts
 * // app entry, instead of calling this function
 * import 'virtual:nuxt-icon-bundle/register';
 * ```
 *
 * The plugin registers through `addIcon` from `@iconify/vue`, the same
 * global store `<VCIcon>` resolves against, so no component changes are
 * needed. Scanning this package and `@vuecs/icons-font-awesome` is
 * required: kit components and the identity-provider preset tables hold
 * roughly half the icon names, and the vuecs preset's behavioral defaults
 * (pagination arrows, submit-button icons, alert icons, collapse chevrons)
 * exist only inside that package.
 *
 * Kept for consumers that cannot run a build-time scan.
 *
 * @deprecated prefer the build-time icon bundle described above.
 */
export declare function registerIconCollections(): void;
/**
 * Build the `app.use(vuecs, ...)` install options shared by authup's UI
 * consumers (apps/client-admin-console's vuecs plugin + the embedded SSR app in
 * apps/client-auth-console): the Font Awesome icon preset and the
 * translator-wired submit-button defaults. Themes stay a caller concern —
 * the kit must not depend on the theme packages (the kit theme peers the
 * kit) — and are passed through in the given order (kit theme first, app
 * theme layers on top).
 *
 * MUST be called within an injection context (a component setup, a Nuxt
 * plugin's `setup()`, or `app.runWithContext(...)`) AFTER the kit's
 * `install()` ran — `buildSubmitButtonDefaults()` reads the ilingo locale
 * provider via `inject()`.
 *
 * Defaults for components the kit does not depend on stay with their
 * consumer: a `@vuecs/navigation` key (the breadcrumb landmark label) would
 * only type-check here if the kit declared that package, and it uses none
 * of its components.
 */
export declare function buildVuecsInstallOptions(input?: VuecsInstallOptionsInput): VuecsInstallOptions;
//# sourceMappingURL=module.d.ts.map