Internationalization reference

The generated @jsvision/i18n API documents catalog authoring, translation, formatting, validation, diagnostics, and asynchronous sources. The default entry point is browser-safe; Node file loading is available from @jsvision/i18n/node.

Start with the internationalization guide for a complete application workflow. The generated entry-point index links every Node and official locale subpath to its exported API symbol.

Official locale entry points

Framework packages publish one catalog from each explicit locale subpath:

• @jsvision/ui/locales/{locale}
• @jsvision/forms/locales/{locale}
• @jsvision/files/locales/{locale}
• @jsvision/datagrid/locales/{locale}
• @jsvision/code-editor/locales/{locale}

{locale} is one of en, nl, de, fr, es, it, pt-PT, pl, ro, or sv. Import only the locale your application requests; main package entry points do not include non-English catalogs.

Package compatibility

@jsvision/i18n is ESM-only, supports Node.js 22 or newer, has zero runtime dependencies, and uses the platform Intl implementation. It is owned and released by JSVision rather than wrapping @blendsdk/i18n.

The package README covers BlendSDK migration and links the published third-party notice containing the upstream MIT attribution.