Lingo.dev is an open-source i18n toolkit for Node.js environments, currently at version `0.133.9`, which is actively maintained with frequent patch releases addressing fixes and minor enhancements across its components. It functions as a comprehensive solution for localization, notably leveraging AI to streamline i18n setup in popular React frameworks like Next.js, React Router, and TanStack Start. A key differentiator is its 'MCP' (Multi-Context Planning) feature, which provides AI assistants with structured, framework-specific i18n knowledge to prevent common hallucination errors during setup. The package offers a robust CLI for translating various file formats (JSON, YAML, markdown, CSV, PO, VTT), an SDK for runtime translation, a compiler for build-time localization, and integrates into CI/CD pipelines. This ecosystem covers the full localization lifecycle from initial configuration to automated workflows.
npm install lingo.devVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates basic programmatic interaction with the Lingo.dev SDK for pushing and fetching JSON content, illustrating runtime translation capabilities.
Upgrade your Node.js environment to version 18 or newer.
Update error handling logic to explicitly catch and manage network-related errors that may now propagate from Lingo.dev SDK calls, particularly for the `whoami` function and similar API interactions.
Always import SDK functionalities directly from 'lingo.dev' (e.g., `import { Client } from 'lingo.dev';`) rather than attempting to import from `@lingo.dev/_sdk`.Ensure you are on version `0.133.6` or later to leverage the fix for the CI pull request flow. If using custom CI/CD scripts, verify their idempotency.
Install the CLI globally (`npm install -g lingo.dev`) or use `npx lingo.dev@latest <command>` to execute it without global installation.
Update Lingo.dev to version `0.133.6` or newer, which contains a fix for this VTT parsing issue.
Verify that your `LINGO_API_KEY` and `LINGO_PROJECT_ID` environment variables are correctly set and correspond to valid credentials for your Lingo.dev project.
Ensure the `Lingo.dev Client` is correctly instantiated with valid `apiKey`, `projectId`, and `baseUrl` in its configuration object.