x18n

Universal toolkits for linting, viewing and managing i18n for any frameworks.

x18n is the spiritual successor of i18n-ally, that generalizes its concepts into a framework-agnostic toolkit that runs everywhere with a more robust and extensible architecture.

Features

Works with your project

• 🧩 45+ Presets, Zero Config - Detects Vue, React, Angular, Svelte, Astro, Next.js, Nuxt, Flutter, Laravel, Rails, .NET and more automatically
• 🗂 Any Format - JSON, JSON5, YAML, PO, Fluent, INI, Properties, PHP and .NET resource files
• 🗃 Namespaces - Organize messages with ns:key style keys
• 🔌 Extensible - Add your own formats, scanners, checks and presets with plugins

Keep it healthy

• ✅ Lint & Check - Missing, unused and invalid keys, placeholder mismatches and glossary violations, ready for CI
• 🕐 Stale Detection - Find translations whose source text changed since they were written
• ⚡ Find Missing - Report and fill in missing keys and translations for any locale
• 🔍 Search by Text - Find the key behind any text in any locale, fuzzy or exact, and jump to where the code uses it
• 📦 Extract Hard Strings - Detect hard-coded strings and move them into locale files

Built for agents and CI

• 🤖 Agent Friendly - Translate and review prompts, plus stable --json output for scripts and agents
• 📝 Review - Prompts and checks for reviewing existing translations

Wherever you work

• 🖥 CLI, UI and Editors - The same engine in the terminal, a browser UI, VS Code, any LSP editor, and Vite and Nuxt DevTools
• 🌍 Inline Annotations & Hover Preview - See every locale of a key right in your code
• 🧭 Go to Definition & Find References - Jump from a key to its messages, or list all of its usages
• 🔁 Migrate from i18n Ally - Bring your existing settings over

Usages

You can use the @x18n/cli package to check, analyze, and manage your i18n resources from the command line.

For example,

pnpx @x18n/cli

would output an overview of the i18n resources,

pnpx @x18n/cli check

would do the linting and checking of your i18n resources, reporting missing keys, or unused keys.

pnpx @x18n/cli usages nav.keys

would list all the usages of the specified key (nav.keys) across your project.

You can also run

pnpx @x18n/cli ui

to have an interactive UI in browser to manage your i18n resources easily.

Additionally, you can also install the VS Code extension for a rendering the translations directly within the editor, enabling inline translation previews, and providing rich "Go to Definition" and "Find References" support for your i18n keys.

For other editors, you can use the Language Server to enable similar features.

Packages

Package	What it is
@x18n/core	Engine that runs in Node and in the browser: domain model, plugin API, analysis, edits
@x18n/builtins	Built-in plugins: formats, locale finders, usage scanners, checks, reporters, presets for popular i18n libraries
@x18n/node	Node.js host: file system, config and plugin loading
@x18n/cli	The CLI, with JSON output for CI and agents
@x18n/lsp	Language server for any LSP editor
@x18n/ui	devframe UI: local dev server, static report, in-browser workspace, VS Code panel, devtools panel
@x18n/devtools	The UI as a panel in Vite DevTools, Nuxt DevTools and devframe hubs
x18n-vscode	VS Code extension on top of the language server

Credits

x18n builds on the ideas of i18n Ally and i18n Ally Next.

Sponsors

License

MIT License © Anthony Fu