@callumdenby/i18next-locize-backend
v1.9.0
Published
backend layer for i18next using locize service
Downloads
4
Maintainers
Readme
This is an i18next backend to be used for locize service. It will load resources from locize server using xhr.
It will allow you to save missing keys containing both default value and context information by calling:
i18next.t(key, defaultValue, tDescription);
i18next.t(key, { defaultValue, tDescription });
Getting started
Source can be loaded via npm, bower or downloaded from this repo.
# npm package
$ npm install i18next-locize-backend
# bower
$ bower install i18next-locize-backend
Wiring up:
import i18next from "i18next";
import Locize from "i18next-locize-backend";
i18next.use(Locize).init(i18nextOptions);
- As with all modules you can either pass the constructor function (class) to the i18next.use or a concrete instance.
- If you don't use a module loader it will be added to
window.i18nextLocizeBackend
Backend Options
IMPORTANT make sure you do not add your apiKey in the production build to avoid misuse by strangers
{
// the id of your locize project
projectId: '[PROJECTID]',
// add an api key if you want to send missing keys
apiKey: '[APIKEY]',
// the reference language of your project
referenceLng: '[LNG]',
// version - defaults to latest
version: '[VERSION]',
// private - set to true if you version on locize is set to use private publish
private: false,
// hostnames that are allowed to create, update keys
// please keep those to your local system, staging, test servers (not production)
allowedAddOrUpdateHosts: ['localhost']
}
To load translations only projectId
needs to be filled. To use the saveMissing feature of i18next additional to the projectId both apiKey
and referenceLng
have to be set.
Options can be passed in:
preferred - by setting options.backend in i18next.init:
import i18next from "i18next";
import Locize from "i18next-locize-backend";
i18next.use(Locize).init({
backend: options
});
on construction:
import Locize from "i18next-locize-backend";
const locize = new Locize(options);
via calling init:
import Locize from "i18next-locize-backend";
const locize = new Locize();
locize.init(options);
Additional API endpoints
backend.getLanguages
Will return a list of all languages in your project including percentage of translations done per version.
import Locize from "i18next-locize-backend";
const locize = new Locize(options);
locize.getLanguages((err, data) => {
/*
data is:
{
"en": {
"name": "English",
"nativeName": "English",
"isReferenceLanguage": true,
"translated": {
"latest": 1
}
},
"de": {
"name": "German",
"nativeName": "Deutsch",
"isReferenceLanguage": false,
"translated": {
"latest": 0.9
}
}
}
*/
});
// or
i18next.services.backendConnector.backend.getLanguages(callback);
backend.getOptions
Will return an object containing useful informations for the i18next init options.
import Locize from "i18next-locize-backend";
const locize = new Locize(options);
locize.getOptions((err, data) => {
/*
data is:
{
fallbackLng: 'en',
referenceLng: 'en',
whitelist: ['en', 'de'],
load: 'languageOnly|all' // depending on your whitelist has locals having region like en-US
}
*/
});
// or
i18next.services.backendConnector.backend.getOptions(callback);
You can set a threshold for languages to be added to whitelist by setting whitelistThreshold in backend options (eg: 1 = 100% translated, 0.9 = 90% translated).
SPECIAL - let the backend determine some options to improve loading
You can load some information from the backend to eg. set whitelist for i18next just supporting languages you got in your locize project.
You will get i18next options for (same as above backend.getOptions):
- fallbackLng
- whitelist
- load
import i18next from "i18next";
import Locize from "i18next-locize-backend";
const locize = new Locize(
{
projectId: "[PROJECTID]",
apiKey: "[APIKEY]",
version: "[VERSION]"
// referenceLng -> not needed as will be loaded from API
},
(err, opts) => {
i18next.use(locize).init({ ...opts, ...yourOptions }); // yourOptions should not include backendOptions!
}
);