Socket
Book a DemoInstallSign in
Socket

@howso/ui-internationalization-utils

Package Overview
Dependencies
Maintainers
0
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@howso/ui-internationalization-utils

A set of functions and types to support our translation efforts

latest
Source
npmnpm
Version
1.0.5
Version published
Maintainers
0
Created
Source

UI Internationalization Utils

A set of functions and types to support our translation efforts.

Usage

To use this package in your application install it via npm.

Installation

Standard package installation makes imports available:

npm i --save-dev @howso/ui-internationalization-utils

Creating Bundles

All bundles should be created in .i18n files collocated with your code. They are often separately than component code itself

Every component that includes unique translations should produce an I18nBundle by creating a object of initial translations:

const en = {
  title: "",
  content: {
    1: { a: "", b: "" },
    2: { c: "", d: "" },
  },
};

That object can then be used to define a type all other languages should match:

type Resource = typeof en;
const fr: Resource = {};
const es: Resource = {};

You can create the I18nBundle's strings property for use in t() using a utility function:

import { getStringsForI18nBundleFromResource } from "@howso/ui-internationalization-utils";
const strings = getStringsForI18nBundleFromResource<Resource>(en);

Your translation function strings can then access your strongly typed bundle in this fashion:

import type { FC } from "react";
import { useTranslation } from "react-i18next";
import bundle from "./Component.i18n.ts";

const Component: FC = () => {
    const { t } = useTranslation(bundle.namespace);
    return (<p>{t(bundle.strings.content.1.a)}</p>)
}

Creating a full bundle with multiple languages:

import { I18nBundle } from "@howso/ui-internationalization-utils";
import { Languages } from "@/constants";

export const componentBundle: I18nBundle<Languages, Resource> = {
  namespace,
  resources: { en, fr, es },
  strings: getStringsForI18nBundleFromResource<Resource>(en),
};

Installing bundles

You may use standard index bundling techniques to export bundling:

export * from "./ComponentA.i18n";
export * from "./ComponentB.i18n";

The final set of bundles can be installed into your i18n service:

import i18n from "i18next";
import * as ComponentsI18nBundles from "./components/i18n";
import * as PagesI18nBundles from "./pages/i18n";

i18n
  // ...
  .init({
    resources: addI18nBundlesToResources(resources, [
      ...Object.values(ComponentsI18nBundles),
      ...Object.values(PagesI18nBundles),
    ]),
    // ...
  });

Publishing

This package is published into a private npm registry.

Documentation changes do not require a version publishing. For functional changes, follow SemVer standards updating the package.json and package-lock.json files in your pull request.

When you are ready to publish a new version, use the Github Release action.

FAQs

Package last updated on 19 Sep 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts