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

mcms-node-localization

v0.0.10

Published

mcms node localization module

Downloads

16

Readme

mcms-node-localization

localization module for mcms-node

What does it do

This package allows you to add localization files to your Node project. You can store the localization files in different directories and add them asynchronously as needed. You can use it as a standalone library or in conjunction with a framework like Express.

Why another localization library

Simply because i couldn't find one that fits my workflow. Most libraries have a lot of features but are highly opinionated on how you need to work. Currently my need is for a localization library that can add translations incrementally in different parts of my project. Also, i like to break my localization variables into multiple files for better organization, something that most other libraries don't support.

Install

npm install mcms-node-localization

Folder structure

The library expects a structure like so :

/lang
        /en
            messages.json
        /es
            messages.json

Every file in those folders will be parsed and assigned to an object like so : messages.myTranslationVariable The first part is always the filename and the second your variable.

Usage

check the examples folder for usage scenarios Initialize like so :

var Lang = require('mcms-node-localization');
var locales = ['en','de']; //assuming you have 2 languages
var t = new Lang({
    directory : __dirname + '/locales',
    locales : locales
});

then add the translations

t.add();

Translate using named parameters

console.log(t.get('messages.weekend',{name : 'Michael',surname : 'Bobos'}));

Translate using arguments

console.log(t.get('messages.tree','bob','john'));

Pluralize

console.log(t.choice('messages.cat',2,{name : 'Michael',surname : 'bobos'}));//using named parameters
console.log(t.choice('messages.cat',1,'is enough'));//using arguments

Add new translations at a later stage from a different location

t.add({
    directory : __dirname + '/additionalLocales',
    locales : locales
},function(err,translations){
    console.log(t.get('msg.Hello',{name : 'Michael',surname : 'bobos'}));
});

API

add(options,callback)

where options :

{
    directory : __dirname + '/additionalLocales',
    locales : locales
}

get(translationVariable,optionalArguments)

Where optionalArgument could be an object with named parameters or actual parameters. We are making use of sprintf so if you go for the parameters option make sure they are of the right type.

choice(translationVariable,count,optionalArguments)

Count is a number that will output the singular or plural option of the translation variable. Where optionalArgument could be an object with named parameters or actual parameters. We are making use of sprintf so if you go for the parameters option make sure they are of the right type.

inject(translationVariable,value)

Inject an object to an existing translation. You can either inject the full blown object like so :

var newTranslation = {
    en : {
        focus : 'Daniel san EN'
    },
    de : {
        focus : 'Daniel san DE'
    }
};
t.inject('tester',newTranslation);

or just a single variable like so :

var newTranslation2 = {
    en : 'bob EN',
    de : 'bob DE'
};

t.inject('tester.name',newTranslation2);

This method is especially useful if you want to load translations from a DB instead from the disk