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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ngx-runtime-i18n/cli

v2.2.0

Published

CLI extractor and validator for @ngx-runtime-i18n

Readme

@ngx-runtime-i18n/cli

CLI for @ngx-runtime-i18n that scans your source for translation key usage and validates your catalogs against it. Ships as the ngx-i18n binary.

Install

npm i -D @ngx-runtime-i18n/cli

Commands

ngx-i18n extract

Scans source files for all i18n key usages and writes a manifest.

ngx-i18n extract --src src --output translation-manifest.json

| Option | Default | Description | | ---------- | ----------------------------- | ------------------------------------- | | --src | src | Source directory to scan. | | --output | translation-manifest.json | Output manifest JSON file. |

ngx-i18n check

Validates one or more language catalogs against actual key usage: reports missing keys (used in code but absent from a catalog) and unused keys (present in a catalog but never referenced).

ngx-i18n check --catalog public/i18n --langs en,hi,de --src src --fail-on-missing

| Option | Default | Description | | -------------------- | -------------- | -------------------------------------------------------------- | | --catalog | public/i18n | Catalog directory containing <lang>.json files. | | --langs | en | Comma-separated language codes to validate. | | --src | - | Source directory to scan for key usage (skip if using --manifest). | | --manifest | - | Use a pre-computed manifest JSON (from extract) instead of re-scanning. | | --fail-on-missing | false | Exit with code 1 if any catalog is missing keys. | | --fail-on-unused | false | Exit with code 1 if any catalog has unused keys. |

--src or --manifest is required — check refuses to run with neither, rather than silently reporting a clean pass on zero used keys.

Unused keys are always computed against the catalog for the first --langs entry (e.g. --langs de,fr uses de as the reference) and printed as an informational listing even without --fail-on-unused; that flag only controls whether their presence fails the run.

A call whose key argument isn't a string literal (a template literal, a variable, ...) can't be statically resolved by either command. Instead of silently vanishing from both "used" and "unused" reporting, it's printed as a ⚠ N i18n call(s) use a dynamic/computed key warning with the exact file:line.

Typical CI usage: run extract once, then check --manifest translation-manifest.json --fail-on-missing per language to catch drift between code and catalogs before merge.

License

MIT