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

@tobyt/i18n

v1.1.3

Published

Simple i18n implementation

Downloads

2

Readme

i18n

i18n is a simple ultra-lightweight internationalisation tool, inspired by br-i18n (bundled with BRJS)

Usage

Add translations

Translations can be added with addTranslations. This can be called multiple times. You could choose to keep all translations in one file at the app root, or keep the files closer to the usage, have separate files per locale etc.

import { addTranslations } from "@tobyt/i18n";

addTranslations("en", {
    "some.key": "some.key"
});

addTranslations("en-US", {
    "some.key": "some.other.value"
})

Set locale

With setLocale you can select the locale for a user. You need to ensure you only set the locale to one for which you have provided translations. The locale string can be a language and region, e.g. "en-GB", or just a language, e.g. "en". When setting a region, the translator will always look up the regional value first before falling back to the language-only translations.

import { setLocale } from "@tobyt/i18n";

setLocale("en-GB");

Lookup translations

import i18n from "@tobyt/i18n";

console.log("translation", i18n("some.key"));

Check whether a translation token exists

With tokenExists you can check whether a translation exists.

import i18n, { tokenExists } from "@tobyt/i18n";

if (tokenExists("some.key.modifier")) {
    console.log("translation", i18n("some.key.modifier"));
} else {
    console.log("translation", i18n("some.key"));
}

Missing translations behaviour

By default, translations are looked up in their regional and language locale only (e.g. de-DE first, de second if not found). If a translation is missing for the language locale, a placeholder (???:some.key:???) is displayed.

If you wish, you can define a fallback locale which is queried if no translation can be found in the user locales (e.g. de-DE first, de second, and finally en).

import { setFallbackLocale } from "@tobyt/i18n";

setFallbackLocale("en");