@k8ordo/i18n

Owns the locale axis of an application. One locale set derives the URL segment, negotiation, the params schema, and the static paths; each message is a function that reads the locale where it is called, so the same line renders on the server and in the browser, and only the messages a page names reach its bundle.

npm GitHub

This site is the demo

Every word from the header to the footer comes from @k8ordo/i18n's message. The greeting below is a message that takes an argument.

Name

Hello.

Locale negotiated from your browser languages: detecting

The argument of greeting(name) is typed by the function written for ja. An en written with different parameters does not compile.

Usage

Define the locale set, register it, write each message with message, and call it. That is all.

Features

Locales in one placedefineLocales(['ja', 'en']) is written once. The default, membership, negotiation, the URL segment, and the [locale] schema all come from it, so there is nowhere to copy the list to.
Owns the first URL segmentThe locale lives in the URL. localize / delocalize put the segment on and take it off, and paramsSchema makes /fr/… a real 404. The rest of the pathname belongs to @k8ordo/router.
Negotiates over a listnegotiate(navigator.languages) and negotiate(parseAcceptLanguage(header)) are the same function: each requested tag in order, exact match, then the same language, then the default.
A message is a functionmessage({ ja, en }) is one message. It does not type-check until every locale is there, and its arguments are typed by the function you wrote. No key list, no dictionary object.
Only what is called shipsMessages are ordinary exports, so a bundler keeps only the ones a module names. Text a Server Component rendered never reaches the client.
The same line on either sideNo provider, no hook. On the server the accepted [locale] is the locale of that render; in the browser the URL is. nav.home() renders the same on both.

Design guide

The guide ships inside the npm package. An AI coding assistant reads the exact installed version out of node_modules/@k8ordo/i18n/docs/.

Home

@k8ordo/i18n

This site is the demo

Every word from the header to the footer comes from @k8ordo/i18n's message. The greeting below is a message that takes an argument.

Name

Hello.

Locale negotiated from your browser languages: detecting

The argument of greeting(name) is typed by the function written for ja. An en written with different parameters does not compile.

Features

Locales in one placedefineLocales(['ja', 'en']) is written once. The default, membership, negotiation, the URL segment, and the [locale] schema all come from it, so there is nowhere to copy the list to.

Owns the first URL segmentThe locale lives in the URL. localize / delocalize put the segment on and take it off, and paramsSchema makes /fr/… a real 404. The rest of the pathname belongs to @k8ordo/router.

Negotiates over a listnegotiate(navigator.languages) and negotiate(parseAcceptLanguage(header)) are the same function: each requested tag in order, exact match, then the same language, then the default.

A message is a functionmessage({ ja, en }) is one message. It does not type-check until every locale is there, and its arguments are typed by the function you wrote. No key list, no dictionary object.

Only what is called shipsMessages are ordinary exports, so a bundler keeps only the ones a module names. Text a Server Component rendered never reaches the client.

The same line on either sideNo provider, no hook. On the server the accepted [locale] is the locale of that render; in the browser the URL is. nav.home() renders the same on both.