Open source · Content & Publishing

Locale Fallback Auditor

Check locale fallbacks and translated fields before a page is published.

v0.1.0 · Node.js 22+ · MIT

Browse the public repository · View releases

Audit translation catalogs and the fallback graph that joins them. It reports the three things a fallback graph quietly gets wrong: content that requires a real translation but is served from another locale, an interpolation placeholder that the source text and a translation disagree about, and a fallback cycle.

This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.

Run the checked-in example

npm install github:edilec/locale-fallback-auditor

Read the result

This installs the public GitHub source; locale-fallback-auditor is not published to npm.

Where this check stops

Enforced bounds. Five configurable limits (maxCatalogBytes, maxCatalogDepth, maxFallbackDepth, maxKeysPerCatalog, maxLocales) and two fixed ones (MAXCONFIGBYTES, MAXPATHLENGTH). Exceeding any of them is an explicit finding or a configuration error, never a silent truncation and never a pass. The defaults are in the docs.

Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.

Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.