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

localize-sync

v1.0.1

Published

Auto translate i18n JSON files using MyMemory API

Downloads

208

Readme

localize-sync

Auto-detect and translate missing i18n JSON keys using the MyMemory API.

Install

npm install -g localize-sync

Or use without installing:

npx localize-sync <command>

How it works

localize-sync treats one JSON file as the source of truth (default: fa.json) and compares all other JSON files in the same directory against it. Missing keys are automatically translated via the MyMemory API.


Commands

| Command | Description | |---|---| | check | Show missing and extra keys across all locale files | | translate | Auto-translate missing keys | | report | Generate a i18n-report.json coverage report | | all | Run check → translate → report in sequence |


Options

| Flag | Alias | Default | Description | |---|---|---|---| | --dir <path> | -d | ./locales | Path to your locales directory | | --source <lang> | -s | fa | Source language filename (without .json) |


Usage

# Check missing keys (source: fa.json, dir: ./locales)
localize-sync check

# Translate missing keys in a custom directory
localize-sync translate --dir ./src/translations

# Use a different source language
localize-sync all --source en

# Combine both options
localize-sync all --dir ./src/i18n --source en

Config file (optional)

Instead of passing flags every time, create an i18n.config.js in your project root:

// i18n.config.js
export default {
  dir: './src/locales',
  source: 'fa',
}

Priority order: CLI flags > i18n.config.js > defaults


Example

Given this structure:

locales/
  fa.json   ← source of truth
  en.json   ← partially translated
  de.json   ← empty

Running localize-sync all will:

  1. Detect missing keys in en.json and de.json
  2. Translate them automatically from Persian
  3. Save a coverage report to i18n-report.json

Report output

{
  "en": {
    "total": 9,
    "translated": 9,
    "coverage": "100%",
    "missingKeys": [],
    "extraKeys": []
  }
}

Notes

  • Translation is powered by MyMemory — free, no API key required
  • A 300ms delay is applied between requests to avoid rate limiting
  • If a translation fails, a ⚠️ MISSING: <original> placeholder is inserted