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

ngx-translate-check

v1.0.2

Published

CLI to test an Angular project using ngx-translate to find missing and unused i18n strings.

Downloads

27

Readme

ngx-translate-check

CLI to test an Angular project using ng-translate to find missing and unused i18n strings.

Issues

Prerequisites

  • Node & NPM

Installing

  $ npm install -g ngx-translate-check

Commands

  • files: Parses project files and i18n files to find amount of usage of i18n strings, outputting to stdout or a json file.

    • Output exports a JSON file, in the format below.
    • The input key shows all i18n strings found in your project .ts, .js and .html files, the amount of times they were found and in which files.
    • The translations key shows all the translation strings defined in each translation file.
    "files-output.json"
    {
      "input": {
        "string1": {
          "amount": 1,
          "files": [ "src/test1.html" ]
        },
        "string2": {
          "amount": 2,
          "files": [ "src/test1.html", "src/test2.html" ]
        },
      },
      "translations": {
        "path/to/translation/en.json": {
          "string1": 1,
          "string2": 1,
          "string3": 1
        },
        "path/to/translation/pt-BR.json": {
          "string1": 1,
          "string2": 1,
          "string4": 1
        },
        ...
      }
    }
  • diff: Receives a JSON file generated by the files command and shows difference between translation files (missing strings between files).

  • diff-input: Receives a JSON file generated by the files command and shows difference between translation and input files (strings in input files but not in translations, strings in translations but not in input files).

More info can be obtained by using the --help argument of the CLI.

Example command usage:

files

  • Wrote to output.json the data obtained from test-project, which includes all strings used in the project and all the strings defined in the translation files.

files

  • Used output.json from the files command to obtain the difference between the defined translation files.

TO-DO List

More commands

  • [x] Difference between translation and project files.

  • [ ] Improve project file parser to obtain missing strings that the current regex does not catch.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Authors

Initial project implementation by Francisco Knebel.

Project idea credits to Arthur Jacobs, who suffered along with Angular development, while we survived reading broken JSON files due to a missing comma.

See the full list of contributors who participated in this project.

License

MIT License. Click here for more information.