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

check-i18n

v1.2.6

Published

Direct and reverse check of translations (Angular) i18n in the local directory with the formation of a report.

Downloads

7

Readme

npm

Check translations script

Script get translations by http/http/local path and compare with local directory. Script has reverse mode (see in Documentation).

Attantion! Deep translation chain keys give better result.

Check include:

  • static translations like "obj.key.key1..."
  • dynamic translations ("obj.key." + value)
    • translations with number at end will be cut automatically (deep = 2)
    • use command with --cutkeys=true to cut translations (tail) and add dot to end for unfounded keys at first iteration (number at end will be cut automatically; deep = 1)
  • use command with --replaceplural=true to use special replace function for plural translations (discription in Documentation)

Optimised for Unix and Windows.

How to use

  • -f or --i18ndir - string - path to lang JSON file (http/https or local)
  • -d or --finddir - string - where to find directory
  • --cutkeys - boolean - repeat search for cut translations
  • --replaceplural - boolean - replace plural keys (see below)
  • --reversesearch - only or boolean:
    • only - start only reverse searching (see in Documentation)
    • boolean - start reverse search at end of main script

Use check-i18n -d=[value] -f=[value].

Example: check-i18n -d=./libs -f=https://site.ru/api/translations/en.json

At the end of process file with results will be in folder. File name will have timestamp attributes.

Documentation

Reverse search

Command will search keys in code and compare with translation JSON.

Command can be used alone (without direct searching).

Check cases (ngx-translate):

  • pipe (key | translate)
  • method .instant(key)
  • method .stream(key)

Cases inqlude:

  • dynamic translations (with dot at end in code; like key.; deep for JSON = 1)
  • plural translations (if use --replaceplural command)

Replace plural translations command

Special function for depricated case in some projects.

Don't add this approach to writing code to your project.

It's not best practice!

Special function what replace keys values from lang JSON file with ending /(_one|_many|_other)$/ to %ending% before find key in directory.

Known issues

Progress was stopped at chunk

Problem was founded with CLI-Progress. Process was stopped at 358 chunk (chunkSize was 5). When I changed chunkSize to 20, problem was resolved.

Case with not rendered cliProgress wasn't checked. Maybe it was max size for chunks or unfixed render problem.

Feedback

If you have troubles You can use GitHub issues.


Licence - Apache-2.0

2020 Barabanov Sergey Konstantinovich