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

@reibo/check-i18n-files

v1.0.11

Published

Check i18n files if they are all the same

Downloads

6

Readme

Check i18n files

npm GitHub npm

CircleCI CircleCI

styled with prettier

Do you have a directory full of i18n files, and sometimes you are missing some translations. But you don't see it?

Than this tool can help you to search which ones are missing.

It go through all files, and at the end it gives an overview which one is ok and which translations are missing.

Install

Get it from npm

npm i -D @reibo/check-i18n-files

Analyze your json files

This will generate a report in the command line

check-i18n-files -d Directory 

Write to a csv file

This will write the values to a csv file

check-i18n-files -d Directory -c

The name of the generated file is i18n

Read and save to json files

This will read a csv file and save them to the according values The name of the file to read is i18n.

check-i18n-files -d Directory -r

arguments

Arguments that can be passed

| Argument | What it does | | ------------------ |----------------------------------------------------| |-d or --dir | The directory containing the translation json files| |-c or --csv | Create a csv out of the translated files | |-w or --write | Read the csv and write to json files | |-s or --seperator | Seperator for the csv files, by default ',' |