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

@u-wave/translate

v1.1.1

Published

Small JS translations with proper pluralization

Downloads

1,838

Readme

@u-wave/translate

Basic key-based translation with pluralization for web apps.

This is intentionally barebones—loading translations, switching languages etc is left to the user. The best way to handle switching languages depends on where the library is used. For React apps, the current language can be stored in a top-level component's state. In server-side Express apps, the current language can be stored on the Request object.

Installation - Usage - API - Related - License: MIT

Build Status Coverage Status npm bundle size

Installation

npm install --save @u-wave/translate

Usage

Using this library looks something like this:

import Translator from '@u-wave/translate';
import pluralizeCs from '@u-wave/translate/plurals/cs';

// Define your strings.
const resources = {
  en: {
    users: {
      guests: '{{count}} guest',
      guests_plural: '{{count}} guests',
    },
  },
  cs: {
    users: {
      guests: '{{count}} návštěvník'
      guests_few: '{{count}} návštěvníci'
      guests_many: '{{count}} návštěvníků'
    },
  },
};

// Create an instance for a language, with a pluralization function.
const translator = new Translator(resources.cs, { plural: pluralizeCs });

const guests = translator.t('users.guests', { count: n });

A Translator instance can be used for a single language. @u-wave/translate comes with pluralization functions for a lot of languages. Pluralization functions are configured using the plural option.

The main way to retrieve translations is using the t() method. The first argument is a string key, which can contain .s for nested property access. The second argument is an object containing interpolation data. Each occurrence of {{propName}} in the translation string is replaced with the appropriate value from the interpolation data object. There is a special interpolation data key named count, which is used for pluralization.

Plural forms for a given key are specified by adding another key, suffixed with _plural (among others):

const { t } = new Translator({
  login: 'Log in',
  register: 'Register',
  online: 'One other user is online',
  online_plural: '{{count}} other users are online'
})

t('login') // 'Log in'
t('register') // 'Register'
t('online', { count: 1 }) // 'One other user is online'
t('online', { count: 2 }) // '2 other users are online'
t('online', { count: 0 }) // '0 other users are online'

In English, there are only two plural forms, so this works. Many languages have more than two plural forms, though. For example, Arabic has forms for zero, one, two, "few", and "many" items.

import pluralizeArabic from '@u-wave/translate/plurals/ar';

const { t } = new Translator({
  online_zero: 'Nobody is online',
  online_one: 'One other user is online',
  online_two: 'Two other users are online',
  // 3-10
  online_few: '{{count}} (a few) other users are online',
  // 11-99
  online_many: '{{count}} (many) other users are online',
  // the rest
  online: '{{count}} other users are online',
}, { plural: pluralizeArabic })

The way this works is that pluralization functions return a string. The key is determined by appending _${plural}. This allows each language to implement arbitrary pluralization.

For convenience, you can leave out the _one suffix. The main key will be used for that plural form by default. Note that that is not correct for all languages—make sure to write the _one suffix in that case. If a key with the _one suffix exists, it is preferred over a suffixless key.

Also for convenience, the _other suffix is aliased as _plural.

The English pluralization for example returns either "one" or "other". Because of those two conveniences, you can do:

({
  duck: '{{count}} duck',
  duck_plural: '{{count}} ducks'
})

instead of:

({
  duck_one: '{{count}} duck',
  duck_other: '{{count}} ducks'
})

API

translator = new Translator(lang, options)

Create a translator instance.

Parameters

  • lang - An object mapping key IDs to translated strings.

     new Translator({ login: 'Log in', register: 'Register' });
  • options - Options for this instance.

    • options.plural - A pluralization function for the current language, mapping a cardinal number n to one of 'zero', 'one', 'two', 'few', 'many', 'other', or some other value representing the plural form. The default function works for English (and many other languages).
    • options.default - A default Translator instance to use if a string is missing. You can use this to fall back to eg. English if another language is incomplete.

translator.t(key, data)

Get the translated string for key interpolated with the values in the data object.

If key is an array, the first available key in the list is used.

translator.parts(key, data)

Get an array containing the literal parts of the translated string for key, alternating with the values in the data object. This allows using non-string data values.

const el = document.createElement('strong')
el.textContent = 'Your Name'

const result = new Translator({ name: 'Name: {{name}}' })
  .parts('name', { name: el })

result.forEach((part) => {
  if (typeof part === 'string') {
    part = document.createTextNode(part)
  }
  document.body.appendChild(par)
})

Related

  • i18next inspired this package, especially the resource and interpolation format.
  • nanotranslate is another very small translation library, but its pluralization support is not suited for all languages.
  • make-plural is used to generate the pluralization functions.

License

MIT