@object-ui/i18n 17.5.0 → 17.6.0

package/dist/pickLocalized.d.ts

@@ -34,3 +34,40 @@
  * `pickLocalized({ en: 'Pricing' }, 'constructor')` is `'Pricing'`, not `''`.
  */
 export declare function pickLocalized(value: unknown, language: string | undefined | null): string;
+/**
+ * Write `next` back into a possibly-localized value as the `language` entry,
+ * preserving every other locale — the write-side inverse of
+ * {@link pickLocalized}.
+ *
+ * An authoring surface that shows one locale in one text input has to answer
+ * two questions, and they are not the same question: which entry to DISPLAY
+ * (`pickLocalized`) and which entry a save REPLACES. Answering the second with
+ * "the whole value" is the data-loss shape this function exists to remove —
+ * `onChange(e.target.value)` straight back over `{ en, zh-CN }` destroys every
+ * locale the author was not looking at, silently, on the first keystroke.
+ *
+ * - Plain string / `null` / `undefined` / array input: there is no map to
+ *   preserve, so the result is `next` itself. A string-valued label keeps
+ *   behaving exactly as it always has.
+ * - Inline locale map: the result is the same map with exactly one entry
+ *   replaced (or added — see {@link localeWriteKey}). Non-string entries and
+ *   unrelated locales are carried across untouched.
+ *
+ * The pairing with `pickLocalized` is the invariant that matters and it is
+ * pinned in `__tests__/setLocalized.test.ts`: for any map and any language,
+ * `pickLocalized(setLocalized(map, lang, s), lang) === s`. If the two functions
+ * ever drift apart, an edit lands in an entry the panel does not display and
+ * the "saved" string vanishes — which is why they live in one file.
+ *
+ * ⚠️ This is the minimal non-destructive write for a SINGLE-locale editor. It
+ * is not a multi-locale authoring UI and does not pretend to be: an author can
+ * only ever reach the entry for the locale they are in.
+ *
+ * Authoring every locale from one surface remains an OPEN product question, and
+ * is deliberately not deferred to a tracker here: the deferral this replaced
+ * named objectui#4163, which closed as completed on 2026-08-15 with the question
+ * still unanswered. A comment pointing at a closed card reads as though the
+ * question were settled somewhere, which is how the previous stale premise in
+ * this area survived unread.
+ */
+export declare function setLocalized(value: unknown, language: string | undefined | null, next: string): string | Record<string, unknown>;

package/dist/pickLocalized.js

@@ -69,3 +69,78 @@ export function pickLocalized(value, language) {
     }
     return String(value);
 }
+/**
+ * The map key an edit made in `language` must be WRITTEN to — the write-side
+ * twin of {@link pickLocalized}'s read limbs.
+ *
+ * It deliberately implements only the first three limbs (exact tag, base
+ * language, region-qualified sibling) and then STOPS. `pickLocalized` continues
+ * into `default` -> `en` -> first value, and those last three limbs must never
+ * be write targets: they are DISPLAY fallbacks that hand back *another*
+ * locale's string. Following them would mean an author editing in `fr`, shown
+ * the `en` entry because the map has no French, saves and overwrites English.
+ * When no entry for the active locale exists the edit ADDS one under the active
+ * tag and every stored entry survives untouched.
+ *
+ * The first three limbs are followed exactly because they identify the entry
+ * the author was actually looking at. Writing `zh` when the map stores `zh-CN`
+ * would leave the edited-away `zh-CN` string in place — invisible in the panel
+ * that just "changed" it, still live for any consumer that asks for `zh-CN`.
+ *
+ * Own properties only, `string` values only, for the same reason every
+ * `pickLocalized` limb narrowed that way in objectui#3907: a locale tag that
+ * names an `Object.prototype` member is not an entry, so it cannot be the entry
+ * the author edited.
+ */
+function localeWriteKey(o, language) {
+    const lang = (language || 'en').trim() || 'en';
+    const base = lang.split('-')[0];
+    const has = (key) => Object.prototype.hasOwnProperty.call(o, key) && typeof o[key] === 'string';
+    if (has(lang))
+        return lang;
+    if (has(base))
+        return base;
+    return Object.keys(o).find((k) => k.split('-')[0] === base && has(k)) ?? lang;
+}
+/**
+ * Write `next` back into a possibly-localized value as the `language` entry,
+ * preserving every other locale — the write-side inverse of
+ * {@link pickLocalized}.
+ *
+ * An authoring surface that shows one locale in one text input has to answer
+ * two questions, and they are not the same question: which entry to DISPLAY
+ * (`pickLocalized`) and which entry a save REPLACES. Answering the second with
+ * "the whole value" is the data-loss shape this function exists to remove —
+ * `onChange(e.target.value)` straight back over `{ en, zh-CN }` destroys every
+ * locale the author was not looking at, silently, on the first keystroke.
+ *
+ * - Plain string / `null` / `undefined` / array input: there is no map to
+ *   preserve, so the result is `next` itself. A string-valued label keeps
+ *   behaving exactly as it always has.
+ * - Inline locale map: the result is the same map with exactly one entry
+ *   replaced (or added — see {@link localeWriteKey}). Non-string entries and
+ *   unrelated locales are carried across untouched.
+ *
+ * The pairing with `pickLocalized` is the invariant that matters and it is
+ * pinned in `__tests__/setLocalized.test.ts`: for any map and any language,
+ * `pickLocalized(setLocalized(map, lang, s), lang) === s`. If the two functions
+ * ever drift apart, an edit lands in an entry the panel does not display and
+ * the "saved" string vanishes — which is why they live in one file.
+ *
+ * ⚠️ This is the minimal non-destructive write for a SINGLE-locale editor. It
+ * is not a multi-locale authoring UI and does not pretend to be: an author can
+ * only ever reach the entry for the locale they are in.
+ *
+ * Authoring every locale from one surface remains an OPEN product question, and
+ * is deliberately not deferred to a tracker here: the deferral this replaced
+ * named objectui#4163, which closed as completed on 2026-08-15 with the question
+ * still unanswered. A comment pointing at a closed card reads as though the
+ * question were settled somewhere, which is how the previous stale premise in
+ * this area survived unread.
+ */
+export function setLocalized(value, language, next) {
+    if (value == null || typeof value !== 'object' || Array.isArray(value))
+        return next;
+    const o = value;
+    return { ...o, [localeWriteKey(o, language)]: next };
+}

package/dist/provider.d.ts

@@ -5,7 +5,7 @@
  */
 import React from 'react';
 import type { i18n as I18nInstance } from 'i18next';
-import { type I18nConfig } from './i18n';
+import { type I18nConfig } from './i18n.js';
 /**
  * `localStorage` key holding the user's explicit language choice.
  *

package/dist/provider.js

@@ -5,8 +5,8 @@
  */
 import React, { createContext, useContext, useEffect, useMemo, useRef, useState } from 'react';
 import { I18nextProvider, useTranslation } from 'react-i18next';
-import { createI18n, getDirection } from './i18n';
-import { builtInLocales } from './locales/index';
+import { createI18n, getDirection } from './i18n.js';
+import { builtInLocales } from './locales/index.js';
 /**
  * `localStorage` key holding the user's explicit language choice.
  *

package/dist/useDisplayLocale.js

@@ -5,8 +5,8 @@
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  */
-import { useLocalization } from './LocalizationContext';
-import { useObjectTranslation } from './provider';
+import { useLocalization } from './LocalizationContext.js';
+import { useObjectTranslation } from './provider.js';
 /**
  * `useDisplayLocale` — the BCP-47 tag that field / cell / metric renderers
  * format numbers and other `Intl` values with.

package/dist/useObjectLabel.d.ts

@@ -88,13 +88,27 @@ export declare function useObjectLabel(): {
         description?: string;
     }) => string | undefined;
     /**
-     * Resolve translated label for a navigation group within an app.
-     * Convention: `{ns}.apps.{appName}.navigation.{groupId}.label`.
+     * Read `{ns}.apps.{appName}.navigation.{groupId}.label` out of the loaded
+     * CLIENT translation resources, falling back to `fallback`.
      *
-     * Mirrors `objectLabel`/`dashboardLabel` so app metadata can keep
-     * English fallbacks while translation packs supply localised
-     * sidebar group labels (e.g. "Sales" → "销售") without explicit
-     * I18nLabel `{ key, defaultValue }` annotations.
+     * ⚠️ This does NOT localize the sidebar, and adding a translation pack
+     * keyed this way will not change a single rendered nav label.
+     * **App-navigation localization is owned solely by the server-side
+     * `/meta` boundary**: `translateApp` in `@objectstack/spec`
+     * (`src/system/i18n-resolver.ts`) rewrites every navigation node's
+     * `label` by id, and `@objectstack/rest` applies it before the metadata
+     * reaches this client — so nav labels arrive already localized. One
+     * owner, not two. To translate a sidebar group, translate it there.
+     *
+     * History (objectui#5197): until then this docstring promised
+     * `"Sales" → "销售"` for sidebar groups, and `NavigationRenderer`
+     * accepted `resolveGroupLabel`/`resolveItemLabel` to wire it up. Those
+     * props could never fire — the renderer's `isCustomized` guard compared a
+     * node's authored label against its own `id` (`Workspace` vs
+     * `grp_workspace`), which never match, so the guard was true for every
+     * real entry. The props are gone; the promise was false, not merely
+     * unused. This helper is kept as a plain key reader for a consumer that
+     * renders navigation itself — it has no first-party caller.
      */
     navGroupLabel: (appName: string, groupId: string, fallback: string) => string;
     /**
@@ -133,6 +147,29 @@ export declare function useObjectLabel(): {
      * Returns undefined when neither metadata nor translation provides one.
      */
     widgetDescription: (dashboardName: string, widgetId: string, fallback?: string) => string | undefined;
+    /**
+     * Resolve a translated metric-widget SUB-CAPTION within a dashboard.
+     * Convention: `{ns}.dashboards.{dashboardName}.widgets.{widgetId}.subCaption`.
+     * Returns undefined when neither metadata nor translation provides one.
+     *
+     * Deliberately its OWN key, not a second reader of `widgets.{id}.description`.
+     * The KPI card renders two authored strings from two different fields — the
+     * shared card header's `widget.description`, and the sub-caption under the
+     * value, which is authored as `widget.options.description` — and the
+     * objectstack#5428 item-4 ruling (2026-08-06) settled that they get two
+     * keys, not one: 「两个作者字段两个 key」. Collapsing them would make one
+     * translation entry silently retarget the other field on any widget type
+     * that renders both at once (`kpi`, `gauge`, `bullet` — every metric-family
+     * type except the self-contained `metric`).
+     *
+     * `subCaption` is the member objectstack#8056 added to the widget
+     * translation node for exactly this, shipped in `@objectstack/spec@17.0.0`.
+     * The server-side resolver reads the SAME key and overlays it onto
+     * `options.description` (`translateDashboard`), so a document served
+     * through `/meta` and a document translated here land on the same string —
+     * this is the client half of one convention, not a second dialect.
+     */
+    widgetSubCaption: (dashboardName: string, widgetId: string, fallback?: string) => string | undefined;
     /**
      * Resolve translated page label, falling back to pageDef.label.
      * Convention: `{ns}.pages.{pageName}.label`.
@@ -311,13 +348,27 @@ export declare function useSafeFieldLabel(): {
         description?: string;
     }) => string | undefined;
     /**
-     * Resolve translated label for a navigation group within an app.
-     * Convention: `{ns}.apps.{appName}.navigation.{groupId}.label`.
+     * Read `{ns}.apps.{appName}.navigation.{groupId}.label` out of the loaded
+     * CLIENT translation resources, falling back to `fallback`.
      *
-     * Mirrors `objectLabel`/`dashboardLabel` so app metadata can keep
-     * English fallbacks while translation packs supply localised
-     * sidebar group labels (e.g. "Sales" → "销售") without explicit
-     * I18nLabel `{ key, defaultValue }` annotations.
+     * ⚠️ This does NOT localize the sidebar, and adding a translation pack
+     * keyed this way will not change a single rendered nav label.
+     * **App-navigation localization is owned solely by the server-side
+     * `/meta` boundary**: `translateApp` in `@objectstack/spec`
+     * (`src/system/i18n-resolver.ts`) rewrites every navigation node's
+     * `label` by id, and `@objectstack/rest` applies it before the metadata
+     * reaches this client — so nav labels arrive already localized. One
+     * owner, not two. To translate a sidebar group, translate it there.
+     *
+     * History (objectui#5197): until then this docstring promised
+     * `"Sales" → "销售"` for sidebar groups, and `NavigationRenderer`
+     * accepted `resolveGroupLabel`/`resolveItemLabel` to wire it up. Those
+     * props could never fire — the renderer's `isCustomized` guard compared a
+     * node's authored label against its own `id` (`Workspace` vs
+     * `grp_workspace`), which never match, so the guard was true for every
+     * real entry. The props are gone; the promise was false, not merely
+     * unused. This helper is kept as a plain key reader for a consumer that
+     * renders navigation itself — it has no first-party caller.
      */
     navGroupLabel: (appName: string, groupId: string, fallback: string) => string;
     /**
@@ -356,6 +407,29 @@ export declare function useSafeFieldLabel(): {
      * Returns undefined when neither metadata nor translation provides one.
      */
     widgetDescription: (dashboardName: string, widgetId: string, fallback?: string) => string | undefined;
+    /**
+     * Resolve a translated metric-widget SUB-CAPTION within a dashboard.
+     * Convention: `{ns}.dashboards.{dashboardName}.widgets.{widgetId}.subCaption`.
+     * Returns undefined when neither metadata nor translation provides one.
+     *
+     * Deliberately its OWN key, not a second reader of `widgets.{id}.description`.
+     * The KPI card renders two authored strings from two different fields — the
+     * shared card header's `widget.description`, and the sub-caption under the
+     * value, which is authored as `widget.options.description` — and the
+     * objectstack#5428 item-4 ruling (2026-08-06) settled that they get two
+     * keys, not one: 「两个作者字段两个 key」. Collapsing them would make one
+     * translation entry silently retarget the other field on any widget type
+     * that renders both at once (`kpi`, `gauge`, `bullet` — every metric-family
+     * type except the self-contained `metric`).
+     *
+     * `subCaption` is the member objectstack#8056 added to the widget
+     * translation node for exactly this, shipped in `@objectstack/spec@17.0.0`.
+     * The server-side resolver reads the SAME key and overlays it onto
+     * `options.description` (`translateDashboard`), so a document served
+     * through `/meta` and a document translated here land on the same string —
+     * this is the client half of one convention, not a second dialect.
+     */
+    widgetSubCaption: (dashboardName: string, widgetId: string, fallback?: string) => string | undefined;
     /**
      * Resolve translated page label, falling back to pageDef.label.
      * Convention: `{ns}.pages.{pageName}.label`.

package/dist/useObjectLabel.js

@@ -17,8 +17,8 @@
  * @module useObjectLabel
  */
 import { useMemo } from 'react';
-import { useObjectTranslation } from './provider';
-import { I18N_PROBE_FLAG } from './i18n';
+import { useObjectTranslation } from './provider.js';
+import { I18N_PROBE_FLAG } from './i18n.js';
 /**
  * Built-in Object UI top-level locale keys — not app namespaces.
  * Update this set when new top-level platform translation keys are added
@@ -30,6 +30,41 @@ const BUILTIN_KEYS = new Set([
     'list', 'kanban', 'chart', 'dashboard', 'configPanel',
     'appDesigner', 'console', 'errors', 'detail',
 ]);
+/**
+ * Whether `i18n` is a real i18next instance rather than react-i18next's
+ * no-instance placeholder.
+ *
+ * With nothing to bind to, `useTranslation` warns `NO_I18NEXT_INSTANCE` and
+ * builds its return value out of a fresh `{}` on every render (`const
+ * finalI18n = i18n || {}`, which then feeds that hook's own `useMemo` deps), so
+ * the `i18n` we receive has a new identity each render even though nothing
+ * about it can have changed.
+ *
+ * `getResourceBundle` is the probe because it is the only instance member the
+ * resolvers below ever touch — via `getAppNamespaces`, the single gate every
+ * `t()` call in this module sits behind.
+ */
+function hasUsableI18nInstance(i18n) {
+    return Boolean(i18n) && typeof i18n?.getResourceBundle === 'function';
+}
+/**
+ * Stand-ins pinned into the memo dependency list while no i18next instance is
+ * bound, so the memo in {@link useObjectLabel} actually holds on the
+ * no-provider path (objectui#5564). Module-level, so they carry one identity
+ * for the lifetime of the process instead of one per render.
+ *
+ * Substituting them is unobservable rather than merely convenient: every `t()`
+ * call in this module sits inside a `for (… of getAppNamespaces())` loop, and
+ * `getAppNamespaces()` returns `[]` under exactly {@link hasUsableI18nInstance}
+ * — so for as long as the substitution is in effect, the closures cannot read
+ * either value at all. `NO_INSTANCE_T` still mirrors react-i18next's own
+ * not-ready `t` (honour a string `defaultValue`, otherwise echo the key) so
+ * that if that reachability argument ever stops holding, behaviour does not
+ * change silently.
+ */
+const NO_INSTANCE_T = ((key, options) => typeof options?.defaultValue === 'string' ? options.defaultValue : key);
+/** @see NO_INSTANCE_T */
+const NO_INSTANCE_I18N = Object.freeze({});
 /**
  * Hook for convention-based auto-resolution of object and field labels.
  *
@@ -46,7 +81,21 @@ const BUILTIN_KEYS = new Set([
  * ```
  */
 export function useObjectLabel() {
-    const { t, i18n } = useObjectTranslation();
+    const { t: boundT, i18n: boundI18n } = useObjectTranslation();
+    // Pin both memo dependencies to module constants while there is no i18next
+    // instance to bind to. Without this the memo below never held on exactly the
+    // no-provider path `useSafeFieldLabel` advertises: react-i18next rebuilds its
+    // return value from a fresh `{}` each render, so `i18n` arrived with a new
+    // identity every time and re-keyed every consumer memo this hook feeds
+    // (objectui#5564 measured 4 distinct identities across 4 renders). See
+    // `hasUsableI18nInstance` for why the substitution cannot be observed.
+    //
+    // When an instance does appear these become the live values again, so a
+    // provider mounting after first render recomputes the object exactly once and
+    // resolves real translations from then on.
+    const bound = hasUsableI18nInstance(boundI18n);
+    const t = bound ? boundT : NO_INSTANCE_T;
+    const i18n = bound ? boundI18n : NO_INSTANCE_I18N;
     // Memoize the entire returned object — all closures below reference `t`/`i18n`
     // and stay valid until the language changes. Returning a fresh object on every
     // render was busting downstream `useMemo`/`useCallback` deps in heavy consumers
@@ -64,7 +113,7 @@ export function useObjectLabel() {
          * (objectui#3372).
          */
         const getAppNamespaces = () => {
-            if (!i18n || typeof i18n.getResourceBundle !== 'function')
+            if (!hasUsableI18nInstance(i18n))
                 return [];
             const lang = i18n.language || 'en';
             const bundle = i18n.getResourceBundle(lang, 'translation');
@@ -267,13 +316,27 @@ export function useObjectLabel() {
                 return resolved || undefined;
             },
             /**
-             * Resolve translated label for a navigation group within an app.
-             * Convention: `{ns}.apps.{appName}.navigation.{groupId}.label`.
+             * Read `{ns}.apps.{appName}.navigation.{groupId}.label` out of the loaded
+             * CLIENT translation resources, falling back to `fallback`.
+             *
+             * ⚠️ This does NOT localize the sidebar, and adding a translation pack
+             * keyed this way will not change a single rendered nav label.
+             * **App-navigation localization is owned solely by the server-side
+             * `/meta` boundary**: `translateApp` in `@objectstack/spec`
+             * (`src/system/i18n-resolver.ts`) rewrites every navigation node's
+             * `label` by id, and `@objectstack/rest` applies it before the metadata
+             * reaches this client — so nav labels arrive already localized. One
+             * owner, not two. To translate a sidebar group, translate it there.
              *
-             * Mirrors `objectLabel`/`dashboardLabel` so app metadata can keep
-             * English fallbacks while translation packs supply localised
-             * sidebar group labels (e.g. "Sales" → "销售") without explicit
-             * I18nLabel `{ key, defaultValue }` annotations.
+             * History (objectui#5197): until then this docstring promised
+             * `"Sales" → "销售"` for sidebar groups, and `NavigationRenderer`
+             * accepted `resolveGroupLabel`/`resolveItemLabel` to wire it up. Those
+             * props could never fire — the renderer's `isCustomized` guard compared a
+             * node's authored label against its own `id` (`Workspace` vs
+             * `grp_workspace`), which never match, so the guard was true for every
+             * real entry. The props are gone; the promise was false, not merely
+             * unused. This helper is kept as a plain key reader for a consumer that
+             * renders navigation itself — it has no first-party caller.
              */
             navGroupLabel: (appName, groupId, fallback) => resolve(`apps.${appName}.navigation.${groupId}.label`, fallback),
             /**
@@ -314,6 +377,33 @@ export function useObjectLabel() {
                 const resolved = resolve(dashboardSuffixes(dashboardName, `widgets.${widgetId}.description`), fb);
                 return resolved || undefined;
             },
+            /**
+             * Resolve a translated metric-widget SUB-CAPTION within a dashboard.
+             * Convention: `{ns}.dashboards.{dashboardName}.widgets.{widgetId}.subCaption`.
+             * Returns undefined when neither metadata nor translation provides one.
+             *
+             * Deliberately its OWN key, not a second reader of `widgets.{id}.description`.
+             * The KPI card renders two authored strings from two different fields — the
+             * shared card header's `widget.description`, and the sub-caption under the
+             * value, which is authored as `widget.options.description` — and the
+             * objectstack#5428 item-4 ruling (2026-08-06) settled that they get two
+             * keys, not one: 「两个作者字段两个 key」. Collapsing them would make one
+             * translation entry silently retarget the other field on any widget type
+             * that renders both at once (`kpi`, `gauge`, `bullet` — every metric-family
+             * type except the self-contained `metric`).
+             *
+             * `subCaption` is the member objectstack#8056 added to the widget
+             * translation node for exactly this, shipped in `@objectstack/spec@17.0.0`.
+             * The server-side resolver reads the SAME key and overlays it onto
+             * `options.description` (`translateDashboard`), so a document served
+             * through `/meta` and a document translated here land on the same string —
+             * this is the client half of one convention, not a second dialect.
+             */
+            widgetSubCaption: (dashboardName, widgetId, fallback) => {
+                const fb = fallback ?? '';
+                const resolved = resolve(dashboardSuffixes(dashboardName, `widgets.${widgetId}.subCaption`), fb);
+                return resolved || undefined;
+            },
             /**
              * Resolve translated page label, falling back to pageDef.label.
              * Convention: `{ns}.pages.{pageName}.label`.
@@ -511,8 +601,11 @@ const SAFE_FIELD_LABEL_FALLBACK = {
 export function useSafeFieldLabel() {
     // useObjectLabel delegates to the provider-safe useObjectTranslation (react-
     // i18next falls back to the global instance and never throws), so it needs no
-    // try/catch — wrapping the hook call would violate rules-of-hooks. It already
-    // returns a stable memoized object; the module-level fallback stays as a
-    // defensive default, reached only if it ever returns nullish.
+    // try/catch — wrapping the hook call would violate rules-of-hooks. Its memo
+    // now holds with or without an i18next instance, so the object below is
+    // stable on both paths — it was NOT before objectui#5564, which measured a
+    // fresh object every render outside a provider, i.e. the opposite of what
+    // this wrapper advertises. The module-level fallback stays as a defensive
+    // default, reached only if it ever returns nullish.
     return useObjectLabel() ?? SAFE_FIELD_LABEL_FALLBACK;
 }

package/dist/useSafeTranslation.js

@@ -12,7 +12,7 @@
  * @param defaults - Fallback English translations keyed by i18n key
  * @param testKey - A key to test if i18n is properly configured (must be in defaults)
  */
-import { useObjectTranslation } from './provider';
+import { useObjectTranslation } from './provider.js';
 /**
  * The i18next option that names the string to use when the lookup misses.
  *

package/dist/utils/index.d.ts

@@ -1,4 +1,4 @@
-export { formatDate, formatDateTime, formatRelativeTime, formatCurrency, formatNumber, type DateFormatOptions, type CurrencyFormatOptions, type NumberFormatOptions, } from './formatting';
-export { resolvePlural, formatDateSpec, formatNumberSpec, applyLocaleConfig, type SpecPluralRule, type SpecDateFormat, type SpecNumberFormat, type SpecLocaleConfig, } from './spec-formatters';
-export { isSpecTranslationData, transformSpecTranslations, type SpecTranslationData, } from './spec-translations';
-export { formatDisplayNumber, shouldGroupDisplayNumber, type DisplayNumberFormatOptions, } from './number-display';
+export { formatDate, formatDateTime, formatRelativeTime, formatCurrency, formatNumber, type DateFormatOptions, type CurrencyFormatOptions, type NumberFormatOptions, } from './formatting.js';
+export { resolvePlural, formatDateSpec, formatNumberSpec, applyLocaleConfig, type SpecPluralRule, type SpecDateFormat, type SpecNumberFormat, type SpecLocaleConfig, } from './spec-formatters.js';
+export { isSpecTranslationData, transformSpecTranslations, type SpecTranslationData, } from './spec-translations.js';
+export { formatDisplayNumber, shouldGroupDisplayNumber, type DisplayNumberFormatOptions, } from './number-display.js';

package/dist/utils/index.js

@@ -1,4 +1,4 @@
-export { formatDate, formatDateTime, formatRelativeTime, formatCurrency, formatNumber, } from './formatting';
-export { resolvePlural, formatDateSpec, formatNumberSpec, applyLocaleConfig, } from './spec-formatters';
-export { isSpecTranslationData, transformSpecTranslations, } from './spec-translations';
-export { formatDisplayNumber, shouldGroupDisplayNumber, } from './number-display';
+export { formatDate, formatDateTime, formatRelativeTime, formatCurrency, formatNumber, } from './formatting.js';
+export { resolvePlural, formatDateSpec, formatNumberSpec, applyLocaleConfig, } from './spec-formatters.js';
+export { isSpecTranslationData, transformSpecTranslations, } from './spec-translations.js';
+export { formatDisplayNumber, shouldGroupDisplayNumber, } from './number-display.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/i18n",
-  "version": "17.5.0",
+  "version": "17.6.0",
   "type": "module",
   "sideEffects": false,
   "license": "MIT",
@@ -32,7 +32,7 @@
   "dependencies": {
     "i18next": "^26.3.6",
     "react-i18next": "^17.0.11",
-    "@object-ui/core": "17.5.0"
+    "@object-ui/core": "17.6.0"
   },
   "peerDependencies": {
     "react": "^18.0.0 || ^19.0.0"