Model or dataset
lingodotdev/lingo.dev avatar
lingodotdev/lingo.dev

Lingo.dev: an open source CLI and compiler for repo-based localization

Open-source localization engineering tools. Connects to Lingo.dev localization engineering platform for consistent, quality translations.

5,402 stars813 forksTypeScriptApache-2.0

At a glance

What is it?
The lingodotdev/lingo.dev repository ships a CLI, a React compiler and a Docker entrypoint that connect a codebase to hosted localization engines. It is for teams that want translations to live in the repository rather than in a spreadsheet.
Who is it for?
Adopt Lingo.dev if your translations already live in the repository and you want to connect them to the hosted Lingo.dev platform, or if you are building a React app and want to use its compiler. Do not adopt it if you need a fully offline pipeline: the CLI is a client for a hosted platform and needs an API key.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 7 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • lingodotdev/lingo.dev5,402 ★ · -1
Star history
Repository2026-09-232026-11-15
lingodotdev/lingo.dev5.4k5.4k

-1 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The problem Lingo.dev addresses in a JavaScript repository

Most localization workflows break at the handoff. Strings are extracted into a file, that file is uploaded to a translation service, translations come back in a different shape, and someone reconciles the two by hand. Lingo.dev treats the repository as the source of truth and the platform as a service the repository calls. The repository describes itself as open-source localization engineering tools that connect to the Lingo.dev localization engineering platform for consistent, quality translations. The target reader is a developer or a localization engineer working in TypeScript or JavaScript, for example on a React app. If your stack is a Java backend with .properties bundles and no Node.js runtime anywhere, this is not the tool for you.

Engines, precedence layers and how a request is resolved

The repository's own description positions these tools as the client side of the Lingo.dev localization engineering platform, which it credits with consistent, quality translations. The repository itself holds the client pieces: a packages/ directory, an integrations/ directory, and a root action.yml alongside the Dockerfile for CI use.

Installing the CLI and pushing your first translation

The repository's Dockerfile runs the CLI as npx lingo.dev@latest ci, and the most recent CLI release is [email protected], published on 2026-10-26. The demo/ directory holds example projects for the CLI (demo/new-cli/) and for the compiler (demo/new-compiler-next16/ and demo/new-compiler-vite-react-spa/).

Running lingo.dev ci in Docker and in CI runners

The repository ships a Dockerfile that wraps the CI command. The base image is node:20.12.2-alpine, and the file adds git with a comment explaining that git is required by lingo.dev ci and is not included in the node:alpine base image. The entrypoint runs npx lingo.dev@latest ci and passes the API key, pull request, commit message, pull request title, working directory and process-own-commits flags through environment variables prefixed with LINGODOTDEV_.

dockerfile
FROM node:20.12.2-alpine

RUN apk add --no-cache git

ENTRYPOINT ["sh", "-c", "npx lingo.dev@latest ci \
  --api-key \"$LINGODOTDEV_API_KEY\" \
  --pull-request \"$LINGODOTDEV_PULL_REQUEST\" \
  --commit-message \"$LINGODOTDEV_COMMIT_MESSAGE\" \
  --pull-request-title \"$LINGODOTDEV_PULL_REQUEST_TITLE\" \
  --working-directory \"$LINGODOTDEV_WORKING_DIRECTORY\" \
  --process-own-commits \"$LINGODOTDEV_PROCESS_OWN_COMMITS\""]

Note the version pinning problem. The image fixes Node.js at 20.12.2 but the entrypoint resolves lingo.dev@latest at container start, so two builds of the same image a week apart can run different CLI versions. Pin the CLI version deliberately if you need reproducible runs.

Where Lingo.dev is the wrong choice

The CLI is a client. The repository describes its tools as connecting to the hosted Lingo.dev localization engineering platform, and the Dockerfile's CI entrypoint passes an API key. If your organization cannot send source strings to a third-party endpoint, the repository does not describe an alternative. A second constraint is version drift. The monorepo publishes many packages under the @lingo.dev scope, and the recent releases show three of them moving on the same day at different versions (@lingo.dev/[email protected], @lingo.dev/[email protected] and [email protected] on 2026-10-26). The leading underscore on two of those package names is a fair signal that they are internal build artifacts rather than stable public APIs. If you depend on them directly, expect churn.

How this differs from gettext and from a TMS-first workflow

The closest conventional alternative is a gettext-style pipeline built on PO files, where msgmerge reconciles catalogs locally and a human or a service fills in the fuzzy entries. The other alternative is a translation management system used as the system of record, where developers export strings and the TMS owns the file. Lingo.dev's tools take a different route: they run from the repository, including in CI through the Dockerfile's lingo.dev ci entrypoint, and connect it to the hosted Lingo.dev localization engineering platform.

Editorial conclusion

Adopt Lingo.dev if your translations already live in the repository and you want to connect them to the hosted Lingo.dev platform, or if you are building a React app and want to use its compiler. Do not adopt it if you need a fully offline pipeline: the CLI is a client for a hosted platform and needs an API key. Before committing, verify your project's Lingo.dev configuration, confirm the CLI version you installed, and check the licence file at LICENSE.md for the terms that apply to your use.

Frequently asked questions

What is Lingo.dev?

It is an open source localization toolkit in TypeScript that connects a repository to the Lingo.dev localization engineering platform. The repository ships a CLI, a React compiler and a Docker entrypoint for CI.

What is the Lingo.dev alternative if I cannot use a hosted platform?

The repository describes its tools as connecting to the hosted Lingo.dev localization engineering platform and does not describe a self-hosted alternative, so a local gettext or PO-based pipeline is the option outside this repository.

How do I install the Lingo.dev CLI?

The repository's Dockerfile runs it with npx lingo.dev@latest ci, and the most recent CLI release is [email protected].

Which LLM does Lingo.dev use for translation?

The repository does not say which model is used; translation is handled by the hosted Lingo.dev localization engineering platform the tools connect to.

What file formats can the Lingo.dev CLI handle?

The CLI documentation lives in packages/cli/README.md, which is the place to check for supported formats.

Does the Lingo.dev Docker image pin the CLI version?

No. The Dockerfile fixes the base image at node:20.12.2-alpine but the entrypoint runs npx lingo.dev@latest ci, so the CLI version is resolved when the container starts rather than when the image is built.

Official sources

  1. License: Apache-2.0
  2. lingodotdev/lingo.dev on GitHub
  3. Project website
  4. README
  5. Releases

Was this useful?