菜单
How to use @owlmeans/i18n — the core localization registry (no runtime deps). Auto-invoked when adding translatable strings to a library package, importing from this package, or working with the tier/priority system.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
PK-based supervisor authentication — a development-only login where a holder of one of the project's trusted private keys mints a token for any user id/email (registering them on first use), bypassing external IdPs. Primary use is end-to-end tests. Covers appendSupervisorAuth (server + web), the supervisor plugin, and the @owlmeans/test-ui helpers. Use when wiring or testing supervisor auth.
How to use @owlmeans/web-auth — web client auth plugins that register into @owlmeans/client-auth/manager. Currently ships the development-only PK-based supervisor login form (appendSupervisorAuth). Auto-invoked when importing @owlmeans/web-auth.
Discovery-first, reuse-first workflow for OwlMeans projects. Use BEFORE planning or building any feature, before proposing a third-party library or a custom solution, and after writing code. Find an existing @owlmeans/* package or existing code first; extend before writing new; simplify what you write.
How to scaffold a new OwlMeans Common project — the @owlmeans/create-app CLI (npm/bun/yarn create), its flags, what it generates, and the manual alternative. Use when asked to create/bootstrap/start a new OwlMeans app or set up a fresh project.
Discovery-first, reuse-first workflow for OwlMeans projects. Use BEFORE planning or building any feature, before proposing a third-party library or a custom solution, and after writing code. Find an existing @owlmeans/* package or existing code first; extend before writing new; simplify what you write.
How to scaffold a new OwlMeans Common project — the @owlmeans/create-app CLI (npm/bun/yarn create), its flags, what it generates, and the manual alternative. Use when asked to create/bootstrap/start a new OwlMeans app or set up a fresh project.
| name | i18n |
| description | How to use @owlmeans/i18n — the core localization registry (no runtime deps). Auto-invoked when adding translatable strings to a library package, importing from this package, or working with the tier/priority system. |
| user-invocable | false |
Layer: Core (no runtime deps)
Install: "@owlmeans/i18n": "^0.1.11" in dependencies
Global registration store that packages write into at import time. React clients drain it lazily via @owlmeans/client-i18n. The store is addressed by (ns, resource, language).
| Export | Description |
|---|---|
addI18nLib(lng, resource, data, opts?) | Register library-owned strings (ns defaults to 'lib') |
addI18nApp(lng, resource, data, opts?) | Register app-owned strings (ns defaults to resource name) |
initI18nResource(lng, resource, ns?) | Drain a registered bundle for a language (called by client-i18n) |
SUPPORTED_LNGS | ['en','pl','ru','be','uk','es','de'] — the canonical language set |
DEFAULT_LNG | 'en' |
LIB_NAMESPACE | 'lib' |
I18nTier | Library | App — enum used internally |
I18nConfig | { defaultLng?, defaultNs?, fallbackLng?, supportedLngs? } |
| Tier | Helper | Default ns | When to use |
|---|---|---|---|
| Library | addI18nLib | 'lib' | Any @owlmeans/* package |
| App | addI18nApp | resource name | Project-specific app / shared project package |
App-tier strings deep-merge over Library-tier strings for the same keys at resolution time — this is the override mechanism.
Every package that ships translatable strings exports a side-effect i18n.ts:
// src/i18n.ts
import { addI18nLib } from '@owlmeans/i18n'
import en from './i18n/en.json' with { type: 'json' }
import pl from './i18n/pl.json' with { type: 'json' }
import ru from './i18n/ru.json' with { type: 'json' }
import be from './i18n/be.json' with { type: 'json' }
import uk from './i18n/uk.json' with { type: 'json' }
import es from './i18n/es.json' with { type: 'json' }
import de from './i18n/de.json' with { type: 'json' }
addI18nLib('en', 'my-package', en)
addI18nLib('pl', 'my-package', pl)
addI18nLib('ru', 'my-package', ru)
addI18nLib('be', 'my-package', be)
addI18nLib('uk', 'my-package', uk)
addI18nLib('es', 'my-package', es)
addI18nLib('de', 'my-package', de)
Then re-export from src/index.ts:
export * from './i18n.js'
Keys are plain dot-paths inside a JSON file:
{
"mySection": {
"title": "Title",
"description": "Description"
},
"form-field": "Invalid field"
}
Consumers use useI18nLib('my-package', 'mySection') → t('title') → resolves lib:my-package.mySection.title.
Use the optional opts.ns when keys must live in a namespace other than 'lib':
addI18nLib('en', 'wallet', walletEn, { ns: 'did' })
All packages must ship all 7 languages from SUPPORTED_LNGS. Adding a new key → add it to all 7 files in the same commit.
Nothing at runtime — pure types and helpers.