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

localization-wow

v1.0.4

Published

For all who have a lot to localize and don't want to think up names for constants.

Downloads

6

Readme

Localization WOW!

For all who have a lot to localize and don't want to think up names for constants.

How to use:

  1. Call setupLocalization(activeLocale) once from your entry point to set the active language (where you get that from is up to you, e.g. browser headers or your server's settings).

  2. In your code use one of the following ways to localize values:

    • var hi = Localize({ en:"Hello", de:"Hallo", fr:"Salut" });
    • var hi2 = Localize("Hello|de:Hallo|fr:Salut");
    • var bye = Localize({ en: "Bye", de: "Tschüss", 'de-DE': "Tschüß", fr: "Salut" });
    • var obj = ({ en: objNeutral, de: objGerman, fr: objFrench })[Localize({ en:"en", de:"de", fr:"fr" })] || objNeutral;

Install in your project directory

npm install localization-wow

Use from Typescript

import { Localize, setupLocalization } from 'localization-wow/Localize'; 

setupLocalization('de-DE'); 

const foo = Localize({ en: "Foo", de: "Fuh" }); 

Use from Javascript

var { Localize, setupLocalization } = require('localization-wow/Localize'); 

setupLocalization('de-DE'); 

var foo = Localize({ en: "Foo", de: "Fuh" }); 

More sophisticated keys like en-GB are possible. Should no match be found for the active language, the fallback is the en-US entry (resp. en-us or en or a '?').

This allows you to see and modify the text directly in your source code. No need to come up with names for entries in string tables.

The TypeScript source files are available in the source directory in the package. They have been relocated in version 1.0.4 in order to avoid issues with ts-loader.