You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/cli/README.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,9 @@
58
58
59
59
### Lingo.dev MCP
60
60
61
-
Model Context Protocol server that enables AI coding assistants to set up i18n infrastructure in React applications through natural language prompts.
61
+
Setting up i18n in React apps is notoriously error-prone - even for experienced developers. AI coding assistants make it worse: they hallucinate non-existent APIs, forget middleware configurations, break routing, or implement half a solution before getting lost. The problem is that i18n setup requires a precise sequence of coordinated changes across multiple files (routing, middleware, components, configuration), and LLMs struggle to maintain that context.
62
+
63
+
Lingo.dev MCP solves this by giving AI assistants structured access to framework-specific i18n knowledge. Instead of guessing, your assistant follows verified implementation patterns for Next.js, React Router, and TanStack Start.
62
64
63
65
**Supported IDEs:**
64
66
@@ -96,7 +98,9 @@ The assistant will:
96
98
97
99
### Lingo.dev CLI
98
100
99
-
Open-source CLI for translating apps and content with AI. Supports all industry-standard formats including JSON, YAML, CSV, PO files, and markdown.
101
+
Keeping translations in sync is tedious. You add a new string, forget to translate it, ship broken UI to international users. Or you send JSON files to translators, wait days, then manually merge their work back. Scaling to 10+ languages means managing hundreds of files that constantly drift out of sync.
102
+
103
+
Lingo.dev CLI automates this. Point it at your translation files, run one command, and every locale updates. A lockfile tracks what's already translated, so you only pay for new or changed content. Supports JSON, YAML, CSV, PO files, and markdown.
100
104
101
105
**Setup:**
102
106
@@ -163,7 +167,9 @@ The `provider` field is optional (defaults to Lingo.dev Engine). For custom LLM
163
167
164
168
### Lingo.dev CI/CD
165
169
166
-
Automated translation workflows for CI/CD pipelines. Prevents incomplete translations from reaching production.
170
+
Translations are the feature that's always "almost done." Engineers merge code without updating locales. QA catches missing translations in staging - or worse, users catch them in production. The root cause: translation is a manual step that's easy to skip under deadline pressure.
171
+
172
+
Lingo.dev CI/CD makes translations automatic. Every push triggers translation. Missing strings get filled before code reaches production. No discipline required - the pipeline handles it.
167
173
168
174
**Supported platforms:**
169
175
@@ -236,7 +242,9 @@ env:
236
242
237
243
### Lingo.dev SDK
238
244
239
-
Runtime translation library for dynamic content. Available for JavaScript, PHP, Python, and Ruby.
245
+
Static translation files work for UI labels, but what about user-generated content? Chat messages, product descriptions, support tickets - content that doesn't exist at build time can't be pre-translated. You're stuck showing untranslated text or building a custom translation pipeline.
246
+
247
+
Lingo.dev SDK translates content at runtime. Pass any text, object, or HTML and get back a localized version. Works for real-time chat, dynamic notifications, or any content that arrives after deployment. Available for JavaScript, PHP, Python, and Ruby.
Build-time translation system that makes React apps multilingual without modifying components. Operates during build rather than runtime.
313
+
Traditional i18n is invasive. You wrap every string in `t()` functions, invent translation keys (`home.hero.title.v2`), maintain parallel JSON files, and watch your components bloat with localization boilerplate. It's so tedious that teams delay internationalization until it becomes a massive refactor.
314
+
315
+
Lingo.dev Compiler eliminates the ceremony. Write React components with plain English text. The compiler detects translatable strings at build time and generates localized variants automatically. No keys, no JSON files, no wrapper functions - just React code that happens to work in multiple languages.
0 commit comments