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

react-i18next-translations-manager

v1.0.1

Published

<!-- GETTING STARTED -->

Downloads

2

Readme

Getting Started

react-i18next-translations-manager is a small package that helps users of react-i18n next that utilize local translation files to manage them better. It scans a given directory recursively, to find the translation keys used in the source code. It provides another utility function that given the path of the locale files, returns the translation keys that are not present for each language.

Prerequisites

You must be using react-i18next in your project, along with local translation files. The translation files must be named translation.json and be located under a directory with the locale name.

Example structure:

├── src
│   ├── components
│   │   ├── **/*.tsx
├── public
│   ├── locales
│   │   ├── EN
│   │       ├── translation.json
│   │   ├── FR
│   │       ├── translation.json
│   │   ├── ES
│   │       ├── translation.json
│   ├── images
│   ├── js
│   ├── index.html
├── dist
├── node_modules
├── package.json
├── package-lock.json
└── .gitignore

Installation

  1. Go in your project's root directory
  2. Run the following command
    npm i react-i18next-translations-manager

Example

import {
  findMissingTranslations,
  findTranslations,
} from "react-i18next-translations-manager";

let translations = findTranslations(`../../my-project/src/components`)

/* OUTPUT
[
    "key1",
    "key2",
    "key3",
    "nested.key4",
    ...
]
/*

let missingTranslations = findMissingTranslations(`../../my-project/public/locales`,translations);

/* OUTPUT
{
    "EN":{
        "key1",
        "nested.key4"
        ...
    },
    "GR":{
        "key2"
        "nested.key4",
        ...
    },
    "FR":{
        "key1"
    },
    "ES":{
        "key2"
    }
    ...
}
/*

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE.txt for more information.