A Koa2 middleware to figure out your request's language either by parsing Accept-Language header or by looking at a language cookie's value. request-language plays nicely with L10ns by abstracting all your language setting logic for you.
Port from request-language
npm install koa-request-language --saveUse it as a middleware to koa v2. All options are described below. Your language will be accessed with ctx.language.
import requestLangauge from 'koa-request-language'
import Koa from 'koa'
const app = new Koa()
app.use(requestLanguage({
languages: ['en-US', 'zh-CN'],
cookie: {
name: 'language',
options: { maxAge: 24*3600*1000 },
url: '/languages/{language}'
}
}))
app.use(async ctx => {
const lang = ctx.language
ctx.body = lang
})
...Access all your localizations in ctx.localizations.
import requestLangauge from 'koa-request-language'
import localizations from 'path/to/l10ns/output/all'
import Koa from 'koa'
const app = new Koa()
app.use(requestLanguage({
languages: ['en-US', 'zh-CN'],
cookie: {
name: 'language',
options: { maxAge: 24*3600*1000 },
url: '/languages/{language}'
},
localizations: localizations
}))
app.use(async (ctx, next) => {
// It will use localization from the right language.
const l = ctx.localizations
console.log(l('HELLO_WORLD'))
})
...Define your language tags ordered in highest priority comes first fashion. The language tags must comply with BCP47 standard. The BCP47 language tag consist of at least the following subtags:
en, zh).Hant, Latn).US, CN).Then language tag has the following syntax:
language[-script][-region]Which makes the following language tags en, en-US and zh-Hant-TW all BCP47 compliant. Please note that the script tag refers to language script. Some languages use two character sets instead of one. Chinese is a good example of having two character sets instead of one–it has both traditional characters and simplified characters. And for popular languages that uses two or more scripts please specify the script subtag, because it can make an i18n library fetch more specific locale data.
Setting the cookie property is optional and whenever it is set this middleware will look at the cookie value instead of the Accept-Language header. Setting this cookie property is ideal for application that support more than 1 language and allows users to change language.
Name of the language cookie. It will store the current language tag of the user's session and remain until maxAge expires or changed by cookie.url.
The options are the same options as express uses in res.cookie(name, value. options). Please checkout their documentation.
Set the change language URL. Lets say that you set the value to /languages/{language} in your configurations. If you visit with your browser the URL path /languages/en-US. It will change your language cookie value to en-US. It will redirect back to the origin URL if you send a referrer header and default to / if it don't send a referrer header.
You can optionally set the language using a query string. This option allows you to set the name of the query parameter that triggers the language setting. The default value is language.
The selected language can be unset by setting the language parameter to default.
const middleware = requestLangauge({
languages: ['en-US', 'zh-CN'],
queryName: 'locale', // ?locale=zh-CN will set the language to 'zh-CN'
cookie: {
name: 'language'
}
})Set the L10ns requireLocalizations(language) function. The right language tag will be used and automatically figured out by request-language. L10ns' l() function will be accessible through koa' ctx.localizations. You also need to set a scoped l variable before usage, otherwise L10ns can't update localization keys through code traversal:
app.use(async (ctx, next) => {
const l = ctx.localizations
})MIT