import type { App } from 'vue';
import type { TranslatorInstallOptions } from './types';
/**
 * Three-stage install:
 *
 * 1. `@ilingo/vue` first (provides the `Ilingo` instance + locale `Ref`
 *    and registers the authup catalogs).
 * 2. `@ilingo/validup-vue` next (looks up the instance via inject and
 *    registers its built-in EN/DE/FR/ES validup validation-message
 *    catalogs onto it).
 *
 * `<IFieldValidation>` is imported and registered per-form locally
 * rather than globally — keeps the form's `components: {}` registry as
 * the single source of truth for what's used in its template.
 *
 * Authup-specific catalogs (`authupEntity`, `authupField`,
 * `authupAction`, `authupCommon`, `authupClient`, `authupApp`,
 * `vuecs`, `authupError`) ship through the same `MemoryStore`. The authored
 * translations live in the framework-agnostic `@authup/i18n` package,
 * which already exports them as an ilingo `CatalogNode` (`CATALOGS`) —
 * the canonical ingestion format — so this install just hands it to the
 * store directly with no per-consumer reconstruction.
 *
 * Zod-driven validators flow through `@validup/zod`'s
 * `createValidator()`, which maps each `ZodIssue` to a specific validup
 * `IssueCode` (`too_small` → `MIN_LENGTH` / `MIN_VALUE` based on
 * origin, `too_big` → `MAX_LENGTH` / `MAX_VALUE`, `invalid_format` →
 * `EMAIL` / `URL` / `UUID` / `DATE` / `IP_ADDRESS` / `BASE64` / `JSON`
 * / `PATTERN` per zod's `format` discriminator, `invalid_type` with
 * undefined input → `REQUIRED`, `invalid_value` → `ONE_OF_FAILED`).
 * Specific constraints surface as parameterized catalog templates
 * (`'The minimum length allowed is {{min}}'`, etc.), localized via
 * `@ilingo/validup`'s EN / DE / FR / ES translations.
 *
 * Migrated from the previous `@ilingo/vuelidate`-based install when
 * authup's frontend moved off `vuelidate` to `@validup/vue`.
 */
export declare function installTranslator(app: App, options?: TranslatorInstallOptions): void;
//# sourceMappingURL=install.d.ts.map