Skip to content
Docs

Command palette

Jump to a page or view, or find a todo by name.

Changelog

intl

Request-scoped language: responsibilities, supported exports and extension points.

Markdown

Purpose

Shared i18next configuration recognizes English, German and French. The server creates a request-scoped instance; web and native supply their own resources. On the web a public page's language is its path (/de/privacy); every other page follows the locale cookie, then the default. locale.config.ts is the leaf that names the languages, their URL slugs and translated segments (Internationalization).

Public exports

SubpathTarget
../src/index.ts
./server./src/server.ts
./locale.config./src/locale.config.ts
./locale-paths./src/locale-paths.ts

These paths come from packages/intl/package.json. A . entry is the package root. Conditional targets distinguish platform or type resolution; consumers should import the subpath, not its source file.

How to extend

Add a message to all three catalogs and use the typed translation API. Keep shared locale constants separate from the server entry. Use Intl for user-visible dates and numbers.

Read the request-scoped language guide for the full flow.

Key files

Edit on GitHubDocumentation is in English.
Cookie settings
We use essential cookies to make our app work. With your consent, we also use optional cookies to improve your experience.

Read our Cookie Policy and Privacy Policy.