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 🙏

© 2024 – Pkg Stats / Ryan Hefner

eslint-plugin-unused-i18next-locale-keys

v1.0.2

Published

An ESLint plugin that checks for unused translation keys in JSON locale files and warns or errors when it finds any.

Downloads

2

Readme

ESLint Plugin: Unused Locale Keys

This ESLint plugin checks for unused translation keys in your JSON locale files and warns or errors when it finds any. It's useful for detecting and removing unused translations in your project, keeping your locale files clean and optimized.

Table of Contents

Installation

  1. Install the plugin as a development dependency:
npm install eslint-plugin-unused-locale-keys --save-dev
  1. Add the plugin to your ESLint configuration file (.eslintrc):
{ "plugins": ["unused-locale-keys"] }

Configuration

Add the rule to your ESLint configuration file (.eslintrc) and specify the desired options:

{
  "rules": {
    "unused-locale-keys/no-unused-locale-keys": [
      "error",
      {
        "localesDir": "path/to/your/locales/directory",
        "supportedExtensions": ["js", "jsx", "ts", "tsx"],
        "locales": "en,es,fr",
        "folder": "src"
      }
    ]
  }
}

Usage

Once the plugin is installed and configured, ESLint will automatically check for unused translation keys in your JSON locale files whenever it is run.

To run ESLint manually:

npx eslint path/to/your/src

Or, you can add a script to your package.json file to run ESLint:

{ "scripts": { "lint": "eslint path/to/your/src" } }

Then, run the script with:

npm run lint

Options

The rule accepts an options object with the following properties:

  • localesDir (required): A string representing the path to the directory containing your JSON locale files.
  • supportedExtensions (required): An array of file extensions to search for translation keys (e.g., ["js", "jsx", "ts", "tsx"]).
  • locales (required): A comma-separated string of supported locales (e.g., "en,es,fr").
  • folder (required): A string representing the path to the directory containing your source files.

Examples

Basic Example

Assuming your project structure looks like this:

project-root/
  ├── locales/
  │   ├── en.json
  │   ├── es.json
  │   └── fr.json
  ├── src/
  │   ├── components/
  │   └── utils/
  └── .eslintrc

Configure the plugin in your .eslintrc file:

{
  "plugins": ["unused-locale-keys"],
  "rules": {
    "unused-locale-keys/no-unused-locale-keys": [
      "error",
      {
        "localesDir": "locales",
        "supportedExtensions": ["js", "jsx", "ts", "tsx"],
        "locales": "en,es,fr",
        "folder": "src"
      }
    ]
  }
}

When ESLint runs, it will check for unused keys in the locales/ directory and report any issues it finds.

Custom Configuration Example

If you have a custom project structure or naming conventions, you can adjust the plugin's options accordingly.

For example, let's say your project has a translations/ directory instead of locales/ and uses only TypeScript files:

project-root/
  ├── translations/
  │   ├── en.json
  │   ├── es.json
  │   └── fr.json
  ├── src/
  │   ├── components/
  │   └── utils/
  └── .eslintrc

Configure the plugin in your .eslintrc file:

{
  "plugins": ["unused-locale-keys"],
  "rules": {
    "unused-locale-keys/no-unused-locale-keys": [
      "error",
      {
        "localesDir": "translations",
        "supportedExtensions": ["ts"],
        "locales": "en,es,fr",
        "folder": "src"
      }
    ]
  }
}

In this case, ESLint will search for translation keys only in TypeScript files and check for unused keys in the translations/ directory.

License

MIT License. See the LICENSE file for more details.