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

trnslt

v0.3.1

Published

Micro translation library for dynamic text lookup and substitution

Downloads

265

Readme

Trnslt

An awful mangling of the word translate, but a useful utility for managing app translations.

Installation

Install via npm:

npm install trnslt --save

Usage

The primary, maybe only, use case for trnslt is for in-app string translation.

var Translate = require("trnslt");

var translations = {
  en: {
    titles: {
      index: "Translation Rocks",
      about: "About Us"
    },
    greetings: {
      welcome: "Hello there %{name}!"
    }
  },
  de: {
    titles: {
      index: "Übersetzung ist Groß",
      about: "Über Uns"
    },
    greetings: {
      welcome: "Hallo es %{name}!"
    }
  }
};

var t = new Translate(translations);

t.lookup("en.titles.index"); // 'Translation Rocks'
t.lookup("en.greetings.welcome", (name: "Parker")); // 'Hello there Parker'
t.lookup("de.greetings.welcome", (name: "Parker")); // 'Hallo es Parker!'
t.lookup("en.whatever"); // Error('Unknown translation: en.whatever, whatever')

Localize

You can also initialize Translate with a default language, and use the localize method to fallback on this localization if your requested one failed.

const translations = {
  en: {
    coffee: {
      cold: "Iced Coffee",
      hot: "Hot Coffee",
      unique: "%{description} Coffee"
    }
  },
  ja: {
    coffee: {
      cold: "アイス コーヒー",
      unique: "%{description} コーヒー"
    }
  }
};

const t = new Translate(languageMap, "en");

t.localize("coffee.cold", "ja"); // 'アイス コーヒー'
t.localize("coffee.hot", "ja"); // 'Hot Coffee'
t.localize("coffee.unique", "ja", { description: "すごい" }); // 'すごい  コーヒー'
t.localize("coffee.cold", "en"); // 'Iced Coffee'
t.localize("coffee.unique", { description: "すごい" }); // Error('Must request a locale')
t.localize("coffee.cold"); // Error('Must request a locale')
t.localiez("tea.hot", "ja"); // Error('Unknown translation: ja.tea.hot, tea')

License

See LICENSE.txt