"Effortlessly Track, Validate, and Manage Your Translations."
Welcome to LingoTracker, the ultimate companion to the excellent Transloco library! LingoTracker is designed for anyone looking to efficiently manage translation resources.
Note: LingoTracker is fully functional with a stable API and is currently being validated in an enterprise application. The 1.0 milestone is focused on completing documentation — see the roadmap for details.
LingoTracker ships with an installable skill for AI-powered coding assistants. Run lingo-tracker install-skill to generate a skill file for Claude Code, Cursor, or other agent frameworks. The skill teaches your AI assistant the full i18n workflow: detect untranslated hardcoded strings, find similar existing translations, add translation resources, generate bundles, and update your code to use type-safe key tokens — all without leaving your editor.
Bootstrap translations for new locales in seconds with built-in Google Translate integration. LingoTracker protects ICU placeholders and Transloco variables during translation so {name} and {{ count }} come back intact. Auto-translation triggers automatically when adding or editing resources, or on demand from the CLI and web UI. Learn more.
Every translation moves through a clear status lifecycle: new → translated → verified, with automatic stale detection when the base language value changes. MD5 checksums track both source and translated values, so LingoTracker knows exactly which translations need attention without manual bookkeeping. Use the normalize command to recompute checksums, add missing locale stubs, and clean up empty folders across your entire project.
LingoTracker stores all translations and metadata as JSON files, making it a breeze to review changes in pull requests. Collaborate seamlessly with your team and keep your translation resources organized!
LingoTracker includes a full web application for managing translations visually. Navigate a folder tree sidebar, search across keys and values, and filter by locale or status. Switch between compact and expanded density modes, get similar-translation suggestions as you type in the editor, and trigger auto-translation with a single click. View preferences are persisted per collection so you pick up right where you left off.
# Launch the Tracker web UI
npx lingo-tracker-appLingoTracker is designed with scalability in mind. By storing metadata in separate files and allowing flexible splitting of resources into nested folders, you can manage even the largest resource sets with ease. Whether you're maintaining a handful of translations or managing thousands of keys across dozens of locales, LingoTracker scales with your application.
Built for enterprise workflows, LingoTracker supports multiple collections to organize resources by team, feature, or domain. Collections can be marked read-only — useful for component-library translations vendored under node_modules, which are protected from accidental edits across the CLI, API, and UI (and detected automatically when added). Its CLI-first approach integrates naturally into CI/CD pipelines, enabling automated validation and resource bundling as part of your release process. Combined with Git-friendly storage, teams of any size can collaborate on translations with full traceability and review through their existing pull request workflows.
LingoTracker validates ICU message syntax — balanced braces, placeholder formats, plural/select/number/date expressions, and quote-escape sections — catching errors before they reach production.
When importing translations from external tools or translators, variable and placeholder names within ICU messages are often accidentally translated along with the surrounding text. LingoTracker detects these cases during import and automatically restores the original names, so your translations remain functional without manual cleanup.
Experience compile-time guarantees with generated translation key tokens. This feature ensures that your application uses the correct and valid translation keys, along with type completion, adding an extra layer of confidence to your translations. Learn more.
LingoTracker provides a comprehensive CLI. Its commands add, edit, delete, and move resources, and validate them. Others find similar translations, extract help-translation glossaries, manage protected terms and preferred terminology, and normalize metadata. The rest generate bundles and import or export in JSON and XLIFF. All commands support both interactive (TTY) and non-interactive (CI) modes.
Translating online help or documentation? The glossary command extracts the UI terms mentioned in a block of help text and emits a JSON glossary of their translations across every locale — so help translators reuse the exact terminology already shipped in your app. Feed it a file, a snippet, or piped stdin. Learn more.
lingo-tracker glossary --input help-page.mdBrand names and jargon should stay unchanged through translation. Keep your protected terms in a JSON file, and LingoTracker marks them on export. JSON exports get a doNotTranslate array, and XLIFF exports get a Do not translate: note. On import, LingoTracker rejects any translation that came back with a protected term altered. The terms live in a file of their own, so a terminology list of any size stays out of your configuration diffs. Learn more.
lingo-tracker protected-terms --add iPhone --add "Node.js"Retired a term? Map each discouraged term to the preferred one, with an optional reason. LingoTracker then flags the old term in base-locale text. The resource editor shows a note with a one-click fix, and the CLI, base-locale imports, and validate print warnings. Nothing is blocked. Protected terms keep words intact through translation, but preferred terminology improves the wording of the source text. Learn more.
lingo-tracker preferred-terminology --add "Expenditure" --preferred "Investment"The validate command acts as a quality gate for your release pipeline — it exits with a non-zero code if any resource is new, stale, or untranslated. Add it to GitHub Actions, GitLab CI, or any build system to catch translation gaps before they ship. See the validation docs for CI configuration examples.
Import and export your resource data in JSON and XLIFF 1.2 formats. Use tags to segment resources, filter exports by status or locale, and configure multiple bundles with pattern matching and collection merging strategies. Define collection-level tags in your collection configuration to have every resource in a collection automatically inherit those tags — making cross-collection export filtering effortless. LingoTracker gives you complete control over how you manage and bundle resources for your application.
Install as a dev dependency in your project:
pnpm add -D @simoncodes-ca/lingo-tracker
npm install --save-dev @simoncodes-ca/lingo-tracker
yarn add -D @simoncodes-ca/lingo-tracker# Initialize LingoTracker in your project
npx lingo-tracker init
# Add a translation resource (interactive prompts guide you)
npx lingo-tracker add-resource
# Generate locale bundles and TypeScript key tokens
npx lingo-tracker bundle
# Validate all translations are complete (CI-ready)
npx lingo-tracker validate
# Launch the Tracker web UI
npx lingo-tracker-appCheck the documentation site, the getting started guide for detailed setup instructions, or the full CLI reference for all available commands.
For contributors and AI agents, the architecture documentation covers system design, data models, application layers, and key user flows.
- Technical documentation covering architecture, APIs, and extension points
- Documentation update for accuracy and completeness
- Detailed documentation site published via GitHub Pages
See the full roadmap for future release plans and ideas.
We welcome contributions! Please read our contributing guidelines for more information.
LingoTracker is licensed under the MIT License.
Join us today and redefine the way you manage translations with LingoTracker!