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

@bemedev/internationalization

v0.1.2

Published

https://github.com/chlbri/internationalization.git

Readme

V 0.1.1 Make it browserify

Just one class...

Internationalization

Defaut walkthrough

First create the object with paths (like path.resolve(root, ...parts)) :

const internationalization = new Internationalization(); // {cwd}/src/locales
const internationalization = new Internationalization(
  'my',
  'locales',
  'directory',
); // Path is resolved with process.cwd() as root

NB

  1. The default path is {cwd}/src/locales
  2. The locale must have at least a directory ( locales/{locale}/common.json )
  3. The locales must be json and can be namespaces ( locales/en/firstPage/header.json )

You can init translations sync

const internationalization = new Internationalization();
internationalization.initSync();

Or async

const internationalization = new Internationalization(
  'my',
  'locales',
  'directory',
);
await internationalization.init();

Then, you can get the string by method : getKey

const internationalization = new Internationalization();
internationalization.initSync();
internationalization.getKey('title'); // => Title of the page

Add-ons

Change Language : changeLanguage

By default language is set to English ('en')

const internationalization = new Internationalization();
internationalization.initSync();
internationalization.getKey('title'); // => Title of the page
internationalization.changeLanguage('fr');
internationalization.getKey('title'); // => Titre de la page

Change Default Language : Internationalization.defaultLanguage

By default language is set to English ('en')

Internationalization.defaultLanguage = 'fr';
const internationalization = new Internationalization();
internationalization.initSync();
internationalization.getKey('title'); // => Titre de la page

For tests, go to repo, here

Happy coding 😊❤️😊👨‍💻❤️✅!!