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

@simplelocalize/i18n-key-extract

v1.0.0

Published

A modular CLI tool to extract i18n keys and default translations from your codebase. Supports multiple strategies (i18next, react-intl, data-i18n-key, EJS, Apple, Android, and more) with per-strategy configuration.

Readme

i18n-key-extract

A modular CLI tool to extract i18n keys and default translations from your codebase. Supports multiple strategies (i18next, react-intl, data-i18n-key, EJS, Apple, Android, and more) with per-strategy configuration.

Installation

npm install -g i18n-key-extract

Or use locally:

npm install --save-dev i18n-key-extract

Usage

Basic CLI Usage

i18n-key-extract --strategy <strategy> --src <glob>
  • --strategy (required): Extraction strategy to use. Supported: i18next, react-intl, data-i18n-key, ejs, apple, android.
  • --src (required): Glob pattern for files to scan (e.g. src/**/*.js).
  • --config: Path to a JSON config file for the strategy (optional).
  • --out: Output file for extracted keys (optional).

Example: Extract i18next keys from JS/TS files

i18n-key-extract --strategy i18next --src "src/**/*.{js,ts,jsx,tsx}"

Example: Extract react-intl keys from React files

i18n-key-extract --strategy react-intl --src "src/**/*.{js,jsx,ts,tsx}"

Example: Extract data-i18n-key from HTML

i18n-key-extract --strategy data-i18n-key --src "public/**/*.html"

Example: Use a custom config file

i18n-key-extract --strategy i18next --src "src/**/*.{js,ts}" --config i18next.config.json

Per-Strategy Configuration

Each strategy supports its own config options. You can provide a config file (JSON) via --config or rely on built-in defaults.

Example i18next config (i18next.config.json):

{
  "includeExtensions": [".js", ".ts", ".jsx", ".tsx"],
  "excludeDirs": ["node_modules", "dist"]
}

Example data-i18n-key config (data-i18n-key.config.json):

{
  "selector": "[data-i18n-key]",
  "keyAttr": "data-i18n-key",
  "textAttr": null
}

Output

By default, results are printed to stdout as JSON. Use --out to write to a file:

i18n-key-extract --strategy i18next --src "src/**/*.js" --out keys.json

Supported Strategies

  • i18next: Extracts from t('key', 'Default'), t('key', { defaultValue }), i18nKey attributes.
  • react-intl: Extracts from <FormattedMessage>, <FormattedHTMLMessage>, intl.formatMessage, defineMessages.
  • data-i18n-key: Extracts from HTML elements with data-i18n-key.
  • ejs: Extracts from EJS templates using t('key').
  • apple: Extracts from Apple .strings files.
  • android: Extracts from Android strings.xml files.

Example Output

[
  { "key": "hello", "translation": "Hello world!", "filePath": "src/app.js" },
  { "key": "bye", "translation": "Goodbye!", "filePath": "src/app.js" }
]

Contributing

PRs and issues welcome!

License

MIT