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 🙏

© 2026 – Pkg Stats / Ryan Hefner

multilanguage-handler

v1.1.2

Published

A multi-language handling library to support multi-languages and localization in your app with the simplest most optimized way.

Readme

Multilangauge-Handler for JavaScript

A multi-language handling library to support multi-languages in your app with the simplest most optimized way.

Usage:

This package simply uses json files to store messages. You can do that in 2 simple steps.

Step1 Create a directory for each language in which you will add the json files you want. The directory structure will look something like this:

├── app
    ├── language
        ├── ar
        │   ├── common.json
        │   └── user.json
        ├── en
            ├── common.json
            └── user.json

For example language/en/common.json file will contain:

{
    "success": "Success!",
    "failed": "Sorry something went wrong!"
}

Step2 use the library:

const multilang = require("multilanguage-handler");

multilang.setLang("language/en");
console.log( multilang.get('common.success') );
console.log( multilang.get('common.failed') );

The output for the previous code snippet is:

Success!
Sorry something went wrong!

As you see in the code all you have to do is to call the library then use "setLang" method to choose the directory.

Then use "get" method to get the message and add as a parameter in it the path to the json file separated by dots and the field's name at the end.

In multilang.get('common.success') you are getting the "success" field in the "common.json" file.

And don't worry. No matter how many times you use fields from a single file the library never parses the same file twice (trust me I made sure of it doesn't 😉).

You can also have subdirectories under each language directory if you want.

├── app
    ├── language
        ├── ar
        │   ├── common.json
        │   └── user
        │       └── login.json
        ├── en
            ├── common.json
            └── user
                └── login.json

And get your message the same way:

const multilang = require("multilanguage-handler");

multilang.setLang("language/en");
console.log( multilang.get('user.login.invalid_email') );

License

The MIT License (MIT). Please see License File for more information.