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 🙏

© 2025 – Pkg Stats / Ryan Hefner

i18extract

v3.2.3

Published

extract i18next translation keys from your source code and translate using Google Translate APIs.

Readme

i18extract

A command-line tool for extracting i18next translation keys from your source code and generating translation JSON files using Google Translate APIs.

Badges

npm npm

Table of Contents

Installation

You can use i18extract directly via npx:

npx i18extract

Usage

To extract translation keys and generate translation files, use the following command:

npx i18extract -l en,es,fr -i src/**/*.{js,jsx,ts,tsx} -o locales

Parameters

  • -l (required): List of languages to create translations for (separated by commas, e.g., en,ca,es).
  • -i (required): Input path to search for translation keys (glob patterns can be used).
  • -o (required): Output directory where translation JSON files will be generated.
  • --lint (optional): Checks if every translation key exists in the translation JSON files.

Examples

  1. Basic Usage:

    npx i18extract -l en,es,fr -i src/**/*.{js,jsx,ts,tsx} -o locales

    This command searches the src folder for translation keys (e.g., t('Hi')) and generates:

    • locales/en.json
      { "Hi": "Hi" }
    • locales/es.json
      { "Hi": "Hola" }
    • locales/fr.json
      { "Hi": "Salut" }
  2. Using the Linter:

    npx i18extract -l en,es,fr -i src/**/*.{js,jsx,ts,tsx} -o locales --lint

    This command will check for missing translations:

    >> error: no translation found for "Hi"

License

MIT License

Feel free to let me know if you want to add or modify any sections!