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

i18next-key-inspector

v1.1.0

Published

i18next-key-inspector is a tool that reads JSON-format translation files written for multilingual support to inspect if each locale has the same keys.

Downloads

8

Readme

i18next-key-inspector

i18next-key-inspector is a tool that reads JSON-format translation files written for multilingual support to inspect if each locale has the same keys.

Getting started

Installation

$ npm install --save-dev i18next-key-inspector

i18next-key-inspector.config.json

To compare the keys in translated JSON files using i18next-key-inspector, you must have the i18next-key-inspector.config.json file. You can create a config file at the top level of your project and write it like the example file below.

{
  "basePath": "./public/locales",
  "source": "en",
  "locales": ["ko", "fr", "de"]
}
  • basePath: This is the default path where the translation files for each locale are located. In the example above, JSON-format translation files are located under the path "./public/locales/en".
  • source: This is the source locale. The translation files of other locales are inspect against the source locale.
  • locales: This is the list of locales to compare with the source locale's translation files.

Execution

  • package.json
"scripts": {
    "inspect": "inspect-locale-key"
  },

License

MIT License