@ultimat3/ui 27.3.0 → 27.5.0

package/README.md

@@ -493,7 +493,11 @@ catalog — so every built-in string in the tree renders its key: `<Dialog>`'s c
 `⟦ui.close⟧`, `<Field>`'s marker `⟦ui.required⟧`. The keys are `UI_KEYS`, and they live in the
 framework catalog the SERVER has registered; a browser chunk has none, which is why
 `translatorFor(locale)` on the client is the same empty answer wearing a better name. Send the
-subset the island renders and build the translator from it. `t` itself — `@ultimat3/i18n`'s bare
+subset and build the translator from it — the framework's two halves (`As of 2026-10`, #710):
+the page passes `ui={uiCatalog(t)}` (every `UI_KEYS` template in the request's locale, plurals
+included) and the island renders `<UiProvider t={subsetTranslator(props.ui)}>`, with
+`subsetTranslator` from `@ultimat3/i18n/subset` — an entry that carries no framework catalog, so
+only an island that imports it pays for the lookup. `t` itself — `@ultimat3/i18n`'s bare
 exported function — is not a `Translator` and is `TS2739` in this position.
 
 An island's own copy is a different thing and stays a plain prop: it arrives already translated,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultimat3/ui",
-  "version": "27.3.0",
+  "version": "27.5.0",
   "description": "SolidJS design system: semantic design tokens, dark/RTL-ready SCSS modules, a11y primitives",
   "license": "MIT",
   "type": "module",
@@ -49,10 +49,10 @@
     "icons": "bun run src/icons/build-icons.ts"
   },
   "dependencies": {
-    "@ultimat3/core": "27.3.0",
-    "@ultimat3/i18n": "27.3.0",
-    "@ultimat3/money": "27.3.0",
-    "@ultimat3/time": "27.3.0"
+    "@ultimat3/core": "27.5.0",
+    "@ultimat3/i18n": "27.5.0",
+    "@ultimat3/money": "27.5.0",
+    "@ultimat3/time": "27.5.0"
   },
   "peerDependencies": {
     "solid-js": "^1.9.0"

package/src/index.ts

@@ -422,3 +422,4 @@ export {
   touchTokens,
   zTokens,
 } from './tokens/tokens';
+export { uiCatalog } from './ui-catalog';

package/src/ui-catalog.ts

@@ -0,0 +1,14 @@
+// The design system's own strings, ready to cross into an island. `@ultimat3/ui` resolves every
+// `ui.*` key through the provider's translator, and a translator cannot be an island's prop — so
+// the server resolves all of them once (`uiCatalog(t)`) and the island hands
+// `<UiProvider t={subsetTranslator(props.ui)}>` a translator over them (`@ultimat3/i18n/subset`:
+// only an island that imports it pays for the lookup). The whole namespace, never a per-component pick: which keys a
+// component reads is the design system's business, and an app that listed them guessed.
+
+import type { CatalogSubset, RawTranslator } from '@ultimat3/i18n/subset';
+import { catalogSubset } from '@ultimat3/i18n/subset';
+import { UI_KEYS } from './i18n-keys';
+
+/** Every `ui.*` template in the request's locale, as JSON an island's props can carry. */
+export const uiCatalog = (t: RawTranslator): CatalogSubset =>
+  catalogSubset(t, Object.values(UI_KEYS));