A comprehensive tool for analyzing translation keys in Angular projects using ngx-translate

NextVM i18n — typed translation keys, per-player locale, NUI-aware

Automatically find and export translation keys when editing.

A tool to check and manage translation keys in JSON files

Statically extract translation keys from i18next application.

CLI tool to scan React projects for missing and unused react-i18next translation keys

Minimum viable xgettext .po file generator. Uses a configurable regex to get translation keys.

Configless CLI for finding unused i18next translation keys

Extracting translation keys from Angular HTML and TypeScript files when you use the ngx-translate.

Signal-native, zoneless-first Angular bindings for Etyma: typed translation keys, lazy locale catalogs and SSR transfer.

A packager that will compact all your translation keys onto one single file.

ESLint rules for IO contracts and config: checked fetch responses, parsed boundary data, error cause and taxonomy, zod schema and wire naming, env access, decimal money and translation keys.

AST-based i18n key pruning tool - remove unused translation keys from your locale files

Statically extract translation keys from i18next application.

Checks used translation keys in Angular projects against reference language JSONs.

Scan your code, extract translation keys/values, and merge them into i18n resource files.

Replace i18n translation keys with their values during compilation using babel

CLI tool to find missing translation keys in HTML and JSON files.

This library automatically generates strongly typed translation keys from JSON files for React Native and TypeScript projects. It ensures compile-time safety, preventing errors caused by incorrect translation keys.

Astro bindings for Etyma: typed translation keys, MessageFormat 2 and lazy catalogs on top of Astro's own i18n routing.