npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

dhis2-i18n

v1.0.1

Published

configuration wrapper for i18next translations

Downloads

3

Readme

About

It has default configuration related to Dhis2 project. Upon import i18n is an abstraction on top of i18next library

Install

npm install --save dhis2-i18n

Example

import i18n from 'dhis2-i18n'

import enResources from './i18n/resources/en'
import urResources from './i18n/resources/ur'

// add all languages necessary
i18n.addResources('en', 'translations-app', enResources)
i18n.addResources('ur', 'translations-app', urResources)

i18n.setDefaultNamespace('translations-app')

i18n.changeLanguage('en')
i18n.t('translation string')      // translation string

i18n.changeLanguage('ur')
i18n.t('translation string')      // سٹرنگ کا ترجمعہ

Import

import i18n from 'dhis2-i81n'

Add Language

i18n.addResources(lng, ns, resources)

where,

lng: refers to the language e.g. en, no etc.

ns: Each frontend app will be namespaced. So we don't run into translation conflicts across apps.

resources: set of key value pairs representing a javascript object.

To set the correct namespace in translation resources, the following format will be adopted.

"resources": {
  "en": {
    "frontend-app-name": {
      "translation string": "translation string"
    }
  },
  "ur": {
    "frontend-app-name": {
      "translation string": "سٹرنگ کا ترجمعہ"
    }
  }
}

Set Namespace

i18n.setDefaultNamespace(ns)

for e.g. translations-app the ns value would be translations-app

Change/Set Language

will set the current language for frontend app.

i18n.changeLanguage(lng)

In Code

String passed into i18n.t will translate text w.r.t. current language set.

i18n.t('translation string');