Nectar of the Programming Masses

    TypeScript icon, indicating that this package has built-in type declarations

    1.0.1 • Public • Published


    Library to handle localization in React apps.

    $ npm install la-i18n


    1. Wrap your component tree in a <I18nProvider>, with the i18n attribute set to the instance resulting from init().

      languageImporter is an async function called successively with locale and namespace names. It's your responsibility to load the .json files with translations given these. It is okay to return a failing Promise if the .json file can't be found.

      import { init, I18nProvider } from 'la-i18n'
      const i18n = init({
        languageImporter: async (locale, namespace) => import(`../locales/${locale}/${namespace}.json`),
      export const AppWrapper = ({ children }) => <I18nProvider i18n={i18n}>{children}</I18nProvider>

      Translations will be layered. Basically, the finished strings would be something like:

      const translations = {
        ...(await languageImporter('dev', ns)),
        ...(await languageImporter('en', ns)),
        ...(await languageImporter('en-US', ns)),
    2. Throughout your app, wrap any translatable strings in the <Trans> component, with an i18nKey prop identifying said string.

      import { Trans } from 'la-i18n'
      import { MyHoverEffect } from './other-components'
      const MyHeader = () => (
            {/* Basic usage */}
            <Trans i18nKey="myheader.welcome">Hello world!</Trans>
            {/* This works! The string will reflect simple tags in the translatable messages. */}
            <Trans i18nKey="myheader.subtitle">
              Welcome to the <b>best</b> app in the world.
            {/* This still works. More complex elements will be anonymized and be shown like `<0>this</0>`. */}
            <Trans i18nKey="">
              Learn more about us <MyHoverEffect>now!</MyHoverEffect>
            {/* Yep, still works! Wrap variables in an object to have it be shown as an identifier in the translatable messages. */}
            <Trans i18nKey="myheader.current-user">You're currently logged in as {{ name }}.</Trans>

      If the <Trans> component is not enough (e.g. you need plurals), you can access a full i18next instance calling the useTranslation() hook.

    3. Call the bundled i18n binary to extract the strings from the source files. Use the -l parameter to pass a list of the desired locales.

      The default source file glob is src/**.{js,jsx,ts,tsx,mjs,cjs}, and the default output path is locales/{{locale}}/{{ns}}.json.

      $ npx i18n extract -l en,es
    4. Translate the extracted .json files

    5. Done!

    Detect/change locale

    With the i18n instance resulting from init() or the useTranslation() hook, you can call i18n.changeLanguage("locale"). If you don't pass a locale, one will be detected from the user's browser.




    npm i @xtreamr/la-i18n

    DownloadsWeekly Downloads






    Unpacked Size

    9.84 kB

    Total Files


    Last publish


    • ralliv
    • joelgarcia
    • santimg
    • arnaumarch
    • mancas
    • pacorampas
    • sergio-deka
    • xtreamr-ci
    • nandawtek
    • pblanco-dekalabs
    • mirframai
    • frsela
    • smgaragorri
    • guillaumeparis2000
    • mardito