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

@evgeniy-ost/localizer-cli

v0.0.4

Published

CLI application to help with project localization and language file management

Downloads

24

Readme

Localizer

Instalation

To install Localizer, you need to call

npm install -D @evgenost/localizer

Description

Localizer is small cli application to help add i18n to the application and manage language files. This is not a full-fledged localization tool, it allows you to check the correctness of the localization file or generate a localization file based on the source code of the project.

For example, a project uses a localization function that returns a string translated into the desired language.

// src/source.js
function __(key) {
  // ...code
  // return translation;
}

let translated = __('hello'); // return 'Hello' or 'Привет' depending on the uploaded translation file

The project localization system downloads and uses the translation file in JSON

// locale-en.json
{
  "hello": "Hello!"
}

Localizer will check the source code of the project and compare the keys of all calls to the localization function with the keys of the localization file, point out the differences between them and suggest missing keys.

npx localizer check src/ -t locale-en.json

Use cases

Writing to file

When enabled option '--write' will change the localization file even if there is a difference in the keys. In this case, already translations in the correct keys of the translation file will not be touched.

// src/source.js
function __(key) {
  // ...code
  // return translation;
}

let translated = __('hello');
let title = __('page-title');
// locale-en.json
{
  "hello": "Hello!", // will remain as it is
  "unused-obsolete-key": "bla bla bla" // will removed
  // also will add "page-title":""
}

File structure

Localizer can work with a multi-level structure of a localization file and with a flat structure, as well as change the structure when a special flag is enabled option '--flat'.

// src/source.js
function __(key) {
  // ...code
  // return translation;
}

let translated = __('main.hello-page.title');

The translation file will be

// locale-en.json
{
  "main": {
    "hello-page": {
      "title": "Hello!"
    }
  }
}

When called with the option "--flat"

// locale-en.json
{
  "main.hello-page.title": "Hello!"
}