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

@toil/localize-tui

v0.0.9

Published

a cross-platform utility for interacting with localization files

Readme

@toil/localize-tui

tui-based utility for quick and easy localization

To use:

bunx @toil/localize-tui
npx @toil/localize-tui

Config

The utility can be configured using the localize.config.json or l10n.config.json config in the root of the project (where you will run the utility).

Example of localize.config.json:

{
  "$schema": "https://raw.githubusercontent.com/ilyhalight/localize/refs/heads/master/schema.json",
  "rootPath": "./src",
  "localesDir": "locales",
  "hashFile": "hashes.json",
  "ignoreLocales": ["de"],
  "typesFile": "locales.ts",
  "withTypes": true,
  "parseDotNotation": true,
  "service": "yandexbrowser"
}

rootPath - the path to the folder that will be considered the main folder of the project. For example, if the translation files in the project are in ./src/locales, then the rootPath should be ./src

localesDir - name of the translation folder (default: locales)

hashFile - the name of the file with translation hashes (default: hashes.json)

ignoreLocales - localization files that will be ignored by the utility

typesFile - relative path from localeDir to generated localize types file (default: locales.ts)

withTypes - generate file with typescript localize types

parseDotNotation - parse dot notation in keys (default: true)

For example, if rawPhrase is "key1.key2.key3" and localizedPhrase is "phrase", then

"parseDotNotation": true:

{
  "key1": {
    "key2": {
      "key3": "phrase"
    }
  }
}

"parseDotNotation": false:

{
  "key1.key2.key3": "phrase"
}

service - a service for receiving a translate. Available services:

  • yandexbrowser - [Browser version] Yandex Translate (used by default)
  • yandexcloud - [Cloud version] Yandex Translate
  • yandextranslate - [Website version] Yandex Translate
  • yandexgpt - [Neuro version] Yandex Translate
  • msedge - Microsoft Edge Translate
  • bing - Bing Translate
  • libretranslate - Libre Translate
  • operaaria - Opera Aria AI

Any of these parameters can be removed.

TODO:

  • [x] Generate phrase
  • [x] Delete phrase
  • [x] Get all locales
  • [x] Update hashes
  • [] Diff locales
  • [] Add locale files
  • [] Fun languages

FAQ

Why is spark-md5 used and not crypto-js or the native implementation from NodeJS?

  1. it's faster (~1.35 times)
  2. The native md5 implementation appeared only in NodeJS 21+, which would further increase the startup requirements