@pie-players/pie-assessment-toolkit 0.3.74 → 1.0.0-beta.0

package/dist/runtime/section-runtime-engine-host-context.d.ts

@@ -1,74 +0,0 @@
-/**
- * Cross-Custom-Element context for the section runtime engine (M7 PR 6).
- *
- * The toolkit CE renders inside its own Shadow DOM, so Svelte's native
- * `setContext`/`getContext` (used by `engine-context.ts`) cannot bridge
- * the kernel-provided engine reference to the toolkit's component tree.
- * This module exposes a `@pie-players/pie-context` based context that
- * does cross the CE boundary via DOM events:
- *
- *   - The kernel (`SectionPlayerLayoutKernel.svelte`) installs a
- *     `ContextProvider` for `sectionRuntimeEngineHostContext` on its
- *     `host` (the layout CE). The provider value carries a narrow
- *     lifecycle handle for the engine owned by that kernel mount.
- *   - The toolkit CE installs a `ContextConsumer` on its own host. When
- *     wrapped by a section player layout, the consumer resolves to the
- *     kernel's lifecycle handle and suppresses its standalone lifecycle
- *     DOM emits in favor of the section-player host. Controller-side
- *     calls (`register`, `handleContent*`, `initialize`, etc.) remain
- *     owned by the toolkit's locally-constructed engine. When
- *     standalone, no host provider responds and the toolkit keeps using
- *     its standalone lifecycle path.
- *
- * The two engine-context surfaces (`SECTION_RUNTIME_ENGINE_KEY` and
- * this one) are deliberately distinct:
- *   - `SECTION_RUNTIME_ENGINE_KEY` (Svelte context) stays scoped to a
- *     single component tree (kernel + descendants in the same shadow
- *     root) and is the right hook for in-tree consumers.
- *   - `sectionRuntimeEngineHostContext` (DOM-event context) is the
- *     bridge for cross-CE consumers and only carries data that is safe
- *     to share across CE boundaries (a stable lifecycle handle).
- *
- * **Stability.** This export is part of the stable runtime/engine
- * surface; the symbol identity and value shape are part of the
- * cross-CE contract. Renaming or replacing the symbol is a major
- * breaking change. Adding optional fields to the value shape is
- * allowed; required fields are not.
- */
-/**
- * Narrow cross-CE handle published by section-player. Deliberately omits
- * controller-facing methods (`initialize`, `register`, `handleContent*`,
- * etc.) so the package seam cannot grow an accidental controller contract.
- */
-export interface SectionRuntimeLifecycleHandle {
-    getRuntimeId(): string;
-}
-/**
- * Value shape published by the kernel and consumed by the wrapped
- * toolkit CE. Carries only the lifecycle handle today; if more cross-CE
- * shared runtime state is needed later, fields can be added here
- * additively.
- */
-export interface SectionRuntimeEngineHostContextValue {
-    engine: SectionRuntimeLifecycleHandle;
-}
-/**
- * `pie-context` context key for the cross-CE engine bridge. Uses a
- * `Symbol.for(...)` registry key so providers and consumers in
- * separately-bundled CEs see the same identity.
- */
-export declare const sectionRuntimeEngineHostContext: {
-    __context__: SectionRuntimeEngineHostContextValue;
-};
-export type SectionRuntimeEngineHostContextListener = (value: SectionRuntimeEngineHostContextValue) => void;
-/**
- * Connect a DOM host to the cross-CE engine context through
- * `connectContextWithRetry`, the provider-retry the toolkit's other
- * contexts use.
- *
- * Returns a cleanup function that disconnects the consumer and clears
- * the retry interval. Standalone toolkits naturally exhaust the retry
- * window without ever resolving and continue using their local
- * engine — that is by design and is not an error.
- */
-export declare function connectSectionRuntimeEngineHostContext(host: HTMLElement, onValue: SectionRuntimeEngineHostContextListener): () => void;

package/dist/runtime/section-runtime-engine-host-context.js

@@ -1,57 +0,0 @@
-/**
- * Cross-Custom-Element context for the section runtime engine (M7 PR 6).
- *
- * The toolkit CE renders inside its own Shadow DOM, so Svelte's native
- * `setContext`/`getContext` (used by `engine-context.ts`) cannot bridge
- * the kernel-provided engine reference to the toolkit's component tree.
- * This module exposes a `@pie-players/pie-context` based context that
- * does cross the CE boundary via DOM events:
- *
- *   - The kernel (`SectionPlayerLayoutKernel.svelte`) installs a
- *     `ContextProvider` for `sectionRuntimeEngineHostContext` on its
- *     `host` (the layout CE). The provider value carries a narrow
- *     lifecycle handle for the engine owned by that kernel mount.
- *   - The toolkit CE installs a `ContextConsumer` on its own host. When
- *     wrapped by a section player layout, the consumer resolves to the
- *     kernel's lifecycle handle and suppresses its standalone lifecycle
- *     DOM emits in favor of the section-player host. Controller-side
- *     calls (`register`, `handleContent*`, `initialize`, etc.) remain
- *     owned by the toolkit's locally-constructed engine. When
- *     standalone, no host provider responds and the toolkit keeps using
- *     its standalone lifecycle path.
- *
- * The two engine-context surfaces (`SECTION_RUNTIME_ENGINE_KEY` and
- * this one) are deliberately distinct:
- *   - `SECTION_RUNTIME_ENGINE_KEY` (Svelte context) stays scoped to a
- *     single component tree (kernel + descendants in the same shadow
- *     root) and is the right hook for in-tree consumers.
- *   - `sectionRuntimeEngineHostContext` (DOM-event context) is the
- *     bridge for cross-CE consumers and only carries data that is safe
- *     to share across CE boundaries (a stable lifecycle handle).
- *
- * **Stability.** This export is part of the stable runtime/engine
- * surface; the symbol identity and value shape are part of the
- * cross-CE contract. Renaming or replacing the symbol is a major
- * breaking change. Adding optional fields to the value shape is
- * allowed; required fields are not.
- */
-import { connectContextWithRetry, createContext, } from "@pie-players/pie-context";
-/**
- * `pie-context` context key for the cross-CE engine bridge. Uses a
- * `Symbol.for(...)` registry key so providers and consumers in
- * separately-bundled CEs see the same identity.
- */
-export const sectionRuntimeEngineHostContext = createContext(Symbol.for("pie.sectionRuntimeEngineHostContext"));
-/**
- * Connect a DOM host to the cross-CE engine context through
- * `connectContextWithRetry`, the provider-retry the toolkit's other
- * contexts use.
- *
- * Returns a cleanup function that disconnects the consumer and clears
- * the retry interval. Standalone toolkits naturally exhaust the retry
- * window without ever resolving and continue using their local
- * engine — that is by design and is not an error.
- */
-export function connectSectionRuntimeEngineHostContext(host, onValue) {
-    return connectContextWithRetry(host, sectionRuntimeEngineHostContext, onValue);
-}

package/dist/runtime/stage-emit-gate.d.ts

@@ -1,92 +0,0 @@
-/**
- * Stage-emit suppression gate (M7 PR 6).
- *
- * `PieAssessmentToolkit.svelte` builds a `createStageTracker(...)` whose
- * `emit` callback dispatches the toolkit CE's `pie-stage-change` DOM
- * event and invokes the runtime-tier `onStageChange` callback. PR 6
- * introduces the wrapped/standalone branch:
- *
- *   - **Standalone** (no host lifecycle provider on
- *     the layout CE host): emit + `onStageChange` fire as before.
- *   - **Wrapped** (kernel publishes its lifecycle handle via
- *     `sectionRuntimeEngineHostContext` and the toolkit consumer
- *     resolves it): emit + `onStageChange` are suppressed on the
- *     toolkit CE, because the kernel's engine already emits the
- *     canonical `pie-stage-change` chain on the layout CE host and
- *     invokes the runtime-tier callback. Without suppression the
- *     toolkit CE would also dispatch its own event, which bubbles
- *     through `composed: true` to the layout CE host and produces a
- *     duplicate emission for outside listeners.
- *
- * The internal `stageTracker` latch state advances **before** this
- * helper is reached (the latch is updated inside
- * `createStageTracker.enter` prior to `opts.emit(...)`), so suppression
- * here only short-circuits the externally-visible side effects. The
- * toolkit's own readiness path (`waitUntilReady` / `engine-ready` /
- * `interactive`) keeps working in standalone mode and degenerates into
- * a series of suppressed emits in wrapped mode without losing any
- * latch transitions.
- *
- * Splitting this helper out of the inline `emit:` closure in
- * `PieAssessmentToolkit.svelte` lets us pin the suppression branch in a
- * unit test without mounting the toolkit CE — see
- * `tests/runtime/stage-emit-gate.test.ts`. The closure in the toolkit
- * passes thunks for `isSuppressed` and `getOnStageChange` so the live
- * Svelte reactive variables (`hostLifecycleEngine`, `onStageChange`) are
- * read at emit time, not captured at construction time. This keeps the
- * pre-PR-6 behavior of always reading the latest `onStageChange` prop
- * value (cohort change, host swap, etc.) intact.
- *
- * NOT a public surface: this helper is internal to the toolkit and is
- * not exported from `runtime/engine.ts`. It only exists to make the
- * gate testable.
- */
-import type { StageChangeDetail } from "@pie-players/pie-players-shared/pie";
-export type StageOnChangeHandler = (detail: StageChangeDetail) => void;
-export interface StageEmitGateContext {
-    /**
-     * Reads the current suppression flag. Implemented as a thunk so
-     * the reactive Svelte `$state(hostLifecycleEngine)` is read at emit
-     * time. Return `true` to suppress; `false` to fire.
-     */
-    isSuppressed: () => boolean;
-    /**
-     * Dispatches the `pie-stage-change` DOM event on the toolkit's
-     * CE host. In `PieAssessmentToolkit.svelte` this is the
-     * Svelte-generated `emit("pie-stage-change", detail)` helper.
-     */
-    dispatchDomEvent: (detail: StageChangeDetail) => void;
-    /**
-     * Reads the current `onStageChange` runtime-tier callback. Thunk
-     * so the latest reassigned handler is invoked, not whichever
-     * handler was current at construction time.
-     */
-    getOnStageChange: () => StageOnChangeHandler | null | undefined;
-    /**
-     * Optional logger for handler errors. Defaults to `console.error`
-     * with the same prefix the toolkit used pre-PR-6 so test output
-     * matches production logs.
-     */
-    logHandlerError?: (error: unknown) => void;
-}
-/**
- * Run the toolkit's stage emit pipeline with the suppression gate
- * applied.
- *
- *   - When `isSuppressed()` returns `true`, the helper returns
- *     immediately with neither side effect.
- *   - Otherwise it dispatches the `pie-stage-change` DOM event first,
- *     then invokes `onStageChange(detail)` (preserving the
- *     "DOM-event-then-callback" ordering pre-PR-6 consumers depend
- *     on).
- *   - A throwing `onStageChange` handler does not interrupt the DOM
- *     event (already fired) and does not propagate up to
- *     `stageTracker.enter` (latch state already advanced); the error
- *     is logged and swallowed, matching pre-PR-6 behavior.
- *
- * Returns `true` if the emit pipeline ran (i.e. it was not
- * suppressed); `false` if it was suppressed. Tests use the return
- * value to assert the gate's decision in isolation from the side
- * effects.
- */
-export declare function runStageEmitWithSuppression(context: StageEmitGateContext, detail: StageChangeDetail): boolean;

package/dist/runtime/stage-emit-gate.js

@@ -1,82 +0,0 @@
-/**
- * Stage-emit suppression gate (M7 PR 6).
- *
- * `PieAssessmentToolkit.svelte` builds a `createStageTracker(...)` whose
- * `emit` callback dispatches the toolkit CE's `pie-stage-change` DOM
- * event and invokes the runtime-tier `onStageChange` callback. PR 6
- * introduces the wrapped/standalone branch:
- *
- *   - **Standalone** (no host lifecycle provider on
- *     the layout CE host): emit + `onStageChange` fire as before.
- *   - **Wrapped** (kernel publishes its lifecycle handle via
- *     `sectionRuntimeEngineHostContext` and the toolkit consumer
- *     resolves it): emit + `onStageChange` are suppressed on the
- *     toolkit CE, because the kernel's engine already emits the
- *     canonical `pie-stage-change` chain on the layout CE host and
- *     invokes the runtime-tier callback. Without suppression the
- *     toolkit CE would also dispatch its own event, which bubbles
- *     through `composed: true` to the layout CE host and produces a
- *     duplicate emission for outside listeners.
- *
- * The internal `stageTracker` latch state advances **before** this
- * helper is reached (the latch is updated inside
- * `createStageTracker.enter` prior to `opts.emit(...)`), so suppression
- * here only short-circuits the externally-visible side effects. The
- * toolkit's own readiness path (`waitUntilReady` / `engine-ready` /
- * `interactive`) keeps working in standalone mode and degenerates into
- * a series of suppressed emits in wrapped mode without losing any
- * latch transitions.
- *
- * Splitting this helper out of the inline `emit:` closure in
- * `PieAssessmentToolkit.svelte` lets us pin the suppression branch in a
- * unit test without mounting the toolkit CE — see
- * `tests/runtime/stage-emit-gate.test.ts`. The closure in the toolkit
- * passes thunks for `isSuppressed` and `getOnStageChange` so the live
- * Svelte reactive variables (`hostLifecycleEngine`, `onStageChange`) are
- * read at emit time, not captured at construction time. This keeps the
- * pre-PR-6 behavior of always reading the latest `onStageChange` prop
- * value (cohort change, host swap, etc.) intact.
- *
- * NOT a public surface: this helper is internal to the toolkit and is
- * not exported from `runtime/engine.ts`. It only exists to make the
- * gate testable.
- */
-const defaultLogHandlerError = (error) => {
-    console.error("[pie-assessment-toolkit] onStageChange handler threw", error);
-};
-/**
- * Run the toolkit's stage emit pipeline with the suppression gate
- * applied.
- *
- *   - When `isSuppressed()` returns `true`, the helper returns
- *     immediately with neither side effect.
- *   - Otherwise it dispatches the `pie-stage-change` DOM event first,
- *     then invokes `onStageChange(detail)` (preserving the
- *     "DOM-event-then-callback" ordering pre-PR-6 consumers depend
- *     on).
- *   - A throwing `onStageChange` handler does not interrupt the DOM
- *     event (already fired) and does not propagate up to
- *     `stageTracker.enter` (latch state already advanced); the error
- *     is logged and swallowed, matching pre-PR-6 behavior.
- *
- * Returns `true` if the emit pipeline ran (i.e. it was not
- * suppressed); `false` if it was suppressed. Tests use the return
- * value to assert the gate's decision in isolation from the side
- * effects.
- */
-export function runStageEmitWithSuppression(context, detail) {
-    if (context.isSuppressed()) {
-        return false;
-    }
-    context.dispatchDomEvent(detail);
-    const handler = context.getOnStageChange();
-    if (handler) {
-        try {
-            handler(detail);
-        }
-        catch (error) {
-            (context.logHandlerError ?? defaultLogHandlerError)(error);
-        }
-    }
-    return true;
-}

package/dist/services/ContextVariableStore.d.ts

@@ -1,113 +0,0 @@
-/**
- * Context Variable Store
- *
- * Standalone service for managing QTI 3.0 context variables.
- * Context variables are global assessment-level variables that can be
- * shared across items.
- *
- * Can be used independently by any assessment player without requiring
- * the full AssessmentPlayer.
- *
- * Part of PIE Assessment Toolkit.
- */
-import type { ContextDeclaration } from "@pie-players/pie-players-shared/types";
-/**
- * Standalone service for managing QTI 3.0 context variables.
- *
- * Context variables are global assessment-level variables that can be
- * shared across items. Can be used independently by any assessment player.
- *
- * @example
- * ```typescript
- * // Initialize with declarations
- * const store = new ContextVariableStore(declarations);
- *
- * // Get/set variables
- * const seed = store.get('RANDOM_SEED');
- * store.set('DIFFICULTY_LEVEL', 'hard');
- *
- * // Pass to items
- * const context = store.toObject();
- * await renderItem(item, session, context);
- *
- * // Persist in session
- * session.contextVariables = store.toObject();
- * ```
- */
-export declare class ContextVariableStore {
-    private variables;
-    private declarations;
-    /**
-     * Initialize store with context declarations from assessment
-     *
-     * @param declarations QTI 3.0 context declarations
-     */
-    constructor(declarations?: ContextDeclaration[]);
-    /**
-     * Initialize context variables from declarations
-     *
-     * Sets each variable to its defaultValue or type-appropriate default.
-     */
-    initialize(declarations: ContextDeclaration[]): void;
-    /**
-     * Get context variable value
-     *
-     * @param identifier Variable identifier
-     * @returns Variable value or undefined if not found
-     */
-    get(identifier: string): any;
-    /**
-     * Set context variable value
-     *
-     * @param identifier Variable identifier
-     * @param value New value
-     */
-    set(identifier: string, value: any): void;
-    /**
-     * Check if variable exists
-     */
-    has(identifier: string): boolean;
-    /**
-     * Get all variable names
-     */
-    getIdentifiers(): string[];
-    /**
-     * Get all variables as object (for passing to PIE elements)
-     *
-     * @returns Plain object with all context variables
-     */
-    toObject(): Record<string, any>;
-    /**
-     * Load state from serialized object (for session restore)
-     *
-     * @param state Object containing context variable values
-     */
-    fromObject(state: Record<string, any>): void;
-    /**
-     * Clear all variables (reset to defaults)
-     */
-    reset(): void;
-    /**
-     * Get declaration for variable
-     *
-     * @param identifier Variable identifier
-     * @returns Declaration or undefined if not found
-     */
-    getDeclaration(identifier: string): ContextDeclaration | undefined;
-    /**
-     * Get all declarations
-     */
-    getDeclarations(): ContextDeclaration[];
-    /**
-     * Get default value for QTI base type
-     *
-     * @private
-     */
-    private getDefaultValueForType;
-    /**
-     * Validate value matches declared type (basic validation)
-     *
-     * @private
-     */
-    private validateValue;
-}

package/dist/services/ContextVariableStore.js

@@ -1,206 +0,0 @@
-/**
- * Context Variable Store
- *
- * Standalone service for managing QTI 3.0 context variables.
- * Context variables are global assessment-level variables that can be
- * shared across items.
- *
- * Can be used independently by any assessment player without requiring
- * the full AssessmentPlayer.
- *
- * Part of PIE Assessment Toolkit.
- */
-/**
- * Standalone service for managing QTI 3.0 context variables.
- *
- * Context variables are global assessment-level variables that can be
- * shared across items. Can be used independently by any assessment player.
- *
- * @example
- * ```typescript
- * // Initialize with declarations
- * const store = new ContextVariableStore(declarations);
- *
- * // Get/set variables
- * const seed = store.get('RANDOM_SEED');
- * store.set('DIFFICULTY_LEVEL', 'hard');
- *
- * // Pass to items
- * const context = store.toObject();
- * await renderItem(item, session, context);
- *
- * // Persist in session
- * session.contextVariables = store.toObject();
- * ```
- */
-export class ContextVariableStore {
-    variables = new Map();
-    declarations = new Map();
-    /**
-     * Initialize store with context declarations from assessment
-     *
-     * @param declarations QTI 3.0 context declarations
-     */
-    constructor(declarations) {
-        if (declarations) {
-            this.initialize(declarations);
-        }
-    }
-    /**
-     * Initialize context variables from declarations
-     *
-     * Sets each variable to its defaultValue or type-appropriate default.
-     */
-    initialize(declarations) {
-        this.declarations.clear();
-        this.variables.clear();
-        for (const decl of declarations) {
-            this.declarations.set(decl.identifier, decl);
-            const value = decl.defaultValue ??
-                this.getDefaultValueForType(decl.baseType, decl.cardinality);
-            this.variables.set(decl.identifier, value);
-        }
-        console.debug(`ContextVariableStore: Initialized ${declarations.length} context variables:`, Array.from(this.variables.keys()));
-    }
-    /**
-     * Get context variable value
-     *
-     * @param identifier Variable identifier
-     * @returns Variable value or undefined if not found
-     */
-    get(identifier) {
-        return this.variables.get(identifier);
-    }
-    /**
-     * Set context variable value
-     *
-     * @param identifier Variable identifier
-     * @param value New value
-     */
-    set(identifier, value) {
-        if (!this.declarations.has(identifier)) {
-            console.warn(`ContextVariableStore: Setting undeclared context variable: ${identifier}`, "Consider declaring it in contextDeclarations");
-        }
-        // Type validation (optional but recommended)
-        const decl = this.declarations.get(identifier);
-        if (decl) {
-            this.validateValue(decl, value);
-        }
-        this.variables.set(identifier, value);
-    }
-    /**
-     * Check if variable exists
-     */
-    has(identifier) {
-        return this.variables.has(identifier);
-    }
-    /**
-     * Get all variable names
-     */
-    getIdentifiers() {
-        return Array.from(this.variables.keys());
-    }
-    /**
-     * Get all variables as object (for passing to PIE elements)
-     *
-     * @returns Plain object with all context variables
-     */
-    toObject() {
-        return Object.fromEntries(this.variables);
-    }
-    /**
-     * Load state from serialized object (for session restore)
-     *
-     * @param state Object containing context variable values
-     */
-    fromObject(state) {
-        for (const [key, value] of Object.entries(state)) {
-            this.variables.set(key, value);
-        }
-    }
-    /**
-     * Clear all variables (reset to defaults)
-     */
-    reset() {
-        for (const [identifier, decl] of this.declarations) {
-            const value = decl.defaultValue ??
-                this.getDefaultValueForType(decl.baseType, decl.cardinality);
-            this.variables.set(identifier, value);
-        }
-        console.debug("ContextVariableStore: Reset to default values");
-    }
-    /**
-     * Get declaration for variable
-     *
-     * @param identifier Variable identifier
-     * @returns Declaration or undefined if not found
-     */
-    getDeclaration(identifier) {
-        return this.declarations.get(identifier);
-    }
-    /**
-     * Get all declarations
-     */
-    getDeclarations() {
-        return Array.from(this.declarations.values());
-    }
-    /**
-     * Get default value for QTI base type
-     *
-     * @private
-     */
-    getDefaultValueForType(baseType, cardinality) {
-        if (cardinality === "multiple" || cardinality === "ordered") {
-            return [];
-        }
-        if (cardinality === "record") {
-            return {};
-        }
-        // Single cardinality defaults
-        switch (baseType) {
-            case "boolean":
-                return false;
-            case "integer":
-                return 0;
-            case "float":
-                return 0.0;
-            case "string":
-            case "identifier":
-            case "uri":
-                return "";
-            case "point":
-                return [0, 0];
-            case "pair":
-                return ["", ""];
-            case "directedPair":
-                return ["", ""];
-            case "duration":
-                return 0;
-            case "file":
-                return null;
-            default:
-                return null;
-        }
-    }
-    /**
-     * Validate value matches declared type (basic validation)
-     *
-     * @private
-     */
-    validateValue(decl, value) {
-        // Basic type checking - can be extended
-        if (decl.baseType === "integer" && !Number.isInteger(value)) {
-            console.warn(`ContextVariableStore: Variable ${decl.identifier} expects integer, got:`, typeof value);
-        }
-        if (decl.baseType === "float" && typeof value !== "number") {
-            console.warn(`ContextVariableStore: Variable ${decl.identifier} expects float, got:`, typeof value);
-        }
-        if (decl.baseType === "boolean" && typeof value !== "boolean") {
-            console.warn(`ContextVariableStore: Variable ${decl.identifier} expects boolean, got:`, typeof value);
-        }
-        if ((decl.cardinality === "multiple" || decl.cardinality === "ordered") &&
-            !Array.isArray(value)) {
-            console.warn(`ContextVariableStore: Variable ${decl.identifier} expects array (cardinality: ${decl.cardinality}), got:`, typeof value);
-        }
-    }
-}

package/dist/services/I18nService.d.ts

@@ -1,47 +0,0 @@
-/**
- * I18nService
- *
- * The toolkit's view of the shared i18n provider: a delegating wrapper over
- * `SimpleI18n` from `players-shared` that adds toolkit-scoped logging and wires
- * the lazy catalog loaders.
- *
- * It was once a near-verbatim second copy of that class — same fields, same
- * lookup, same plural selection. Duplicate implementations of one contract drift
- * silently, because nothing fails when only one of them is fixed. Keep this a
- * wrapper.
- *
- * Part of PIE Assessment Toolkit.
- */
-import type { I18nConfig, I18nProvider, I18nServiceApi, InterpolationValues, LocaleCode, MessageCatalog, MessageKeyInput, PluralOptions, TextDirection } from "@pie-players/pie-players-shared/i18n";
-export type { I18nConfig, I18nProvider, I18nServiceApi, InterpolationValues, LocaleCode, MessageCatalog, MessageKeyInput, PluralOptions, TextDirection, };
-/**
- * Toolkit-scoped i18n service.
- *
- * Serves every locale this repository ships, English resident and the rest
- * lazily loaded.
- */
-export declare class I18nService implements I18nServiceApi {
-    private readonly i18n;
-    constructor(config?: I18nConfig);
-    /**
-     * Set the locale, loading its catalog first.
-     *
-     * Never falls back to the browser locale: a rendered-string change reaches a
-     * host's live delivery on their next install with no build signal on their
-     * side, so the locale has to be something the host asked for.
-     */
-    initialize(config: I18nConfig): Promise<void>;
-    t(key: MessageKeyInput, values?: InterpolationValues): string;
-    plural(key: MessageKeyInput, options: PluralOptions): string;
-    getLocale(): string;
-    setLocale(locale: LocaleCode): Promise<void>;
-    getDirection(): TextDirection;
-    getAvailableLocales(): string[];
-    isLocaleLoaded(locale: LocaleCode): boolean;
-    subscribe(listener: () => void): () => void;
-    hasKey(key: MessageKeyInput): boolean;
-    addCustomMessages(locale: string, messages: MessageCatalog): void;
-    withLocale(locale: LocaleCode): I18nProvider;
-    formatNumber(value: number, options?: Intl.NumberFormatOptions): string;
-    formatDate(date: Date, options?: Intl.DateTimeFormatOptions): string;
-}