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

i18next-cli-comment

v1.1.3

Published

Unofficial fork of i18next-cli: same high-performance i18next CLI, with extra comment-based extraction (e.g. per-locale maps in // t(...) comments).

Readme

i18next-cli-comment

Unofficial fork of i18next-cli: same unified, high-performance i18next CLI toolchain (SWC), plus extensions such as per-locale strings inside // t(...) comments. Upstream copyright and license: see LICENSE.

An extension for i18next-cli that adds automatic language tracking and structured output for translation files.

✨ Features

  • 🌍 Automatically tracks used languages
  • 📁 Stores translations in per-language directories (/locales/{lang}/})
  • ✍️ Safely updates files without overwriting other locales
  • ⚙️ Flexible path configuration using templates
  • 🔄 Fully compatible with existing i18next setups

📦 Installation

npm install i18next-cli-comment --save-dev

or

yarn add i18next-cli-comment -D

🚀 Quick Start

Run Initialisation:

npx i18next-cli-comment init

⚙️ Configuration (i18next.config.ts)

| Option | Type | Description | | --------- | -------- | ------------------------------------------------- | | locales | string[] | List of supported languages | | input | string | Input path which directory tracking | | output | string | Output path template (must included {{language}}/{{namespace}}.json) |


🧠 How it works

  1. The CLI scans your project files
  2. Extracts translation keys (e.g. t('key', {en: 'Some words', ua: 'Будь-які слова'}))
  3. Determines active languages
  4. Generates or updates translation files:
/locales
  /en
    translation.json
  /ua
    translation.json
  /de
    translation.json

📄 Example

Source code:

//t('key', {en: 'Some words', ua: 'Будь-які слова'})

Generated output:

locales/en/translation.json

{
  "key": "Some words"
}

locales/ua/translation.json

{
  "key": "Будь-які слова"
}

🔧 CLI Commands(same from i18next-cli)

# extract translations
npx i18next-cli-comment extract

# watch mode 
npx i18next-cli-comment extract --watch

# translation status
npx i18next-cli-comment status

# help
npx i18next-cli-comment help

✅ Benefits

  • Clean and scalable structure
  • Better collaboration in teams

🔮 Roadmap

  • Improve extract method
  • Add support for detecting t() function calls from i18next-cli
  • Fix updating values when new language provided or added

🤝 Contributing

Contributions and suggestions are welcome!