HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
lingodotdev
lingo.dev
TypeScript2024–2025
lingodotdev / lingo.dev

lingo.dev

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

3Distinct people
3Mentions
0Explicit recommenders
5.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month3 dated mentions

Observed mentions: 2024-04-12 12:36:16 UTC to 2025-06-03 17:27:32 UTC.

0122024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsApr 20242024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 20242024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC211
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC000
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC000
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC000
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC000
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC000
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC000
Nov 20242024-11-01 00:00:00 UTC2024-12-01 00:00:00 UTC000
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC000
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC000
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC000
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC000
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC000
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC110

What Hacker News says

2 sources
Hey! Max here, one of the co-founders - great question! Technically - it's a compiler plugin: it augments build artifacts, so that extracting text from the app into JSON files for further translation is no longer required. Since we're solving the problem at compile time, React code remains the same, but the app becomes just one cli command away from being fully translated into other languages! Here's me speedrunning (~2min?) the localization of a typical next js app from english to spanish: https://github.com/replexica/replexica/blob/main/getting-sta...
In Show HN: Replexica – AI-powered internationalization compiler for React (+ API)

Show HN: Replexica – AI-powered internationalization compiler for React (+ API)

Veronica and Max here, we’re building an AI-powered compiler/API for React to help ship multi-language apps faster. Our repo is at https://github.com/replexica/replexica, and the homepage is https://replexica.com. After 9 years of working in tech, we decided to go build our own projects full-time, hoping to ship a new product every month. We failed to make it work, however, we realized the importance of shortcuts when trying to get more users with limited resources. Localization always seemed like such a shortcut: we felt we could’ve onboarded many more international customers who sign up but end up leaving because they couldn’t use them in their native language. However, it really bothered us how much effort we needed to put into setting up localization using react-intl/lingui/react-i18next. It was annoying to extract translatable text f
Read the rest
rom the code and then maintain translation dictionaries. We were also constantly prompt-engineering ChatGPT to produce accurate translations. We made Replexica to automatically traverse React code and understand what needs translation, removing the need to extract strings from the code. That means, you don’t spend time maintaining JSON dictionaries and just focus on shipping features. You just need to plug in Replexica Compiler. We’ve bundled Replexica API with a combination of several LLMs, to produce great translations. We’re using a prompt-engineered GPT-4 to extract the context of the product (e.g., from its website) and the “brand voice”. We’re also using a combination of Llama/GPT/Mixtral for translation. Also, the API spec is open, meaning every developer can build their own translation engine and self-host it. Replexica works seamlessly with Next.js App Router. We’re considering adding support for Next.js Pages Router and Remix.js next. We’d love to hear your feature requests! We opened our repo under the MIT license last week and launched the API. The goal is to not charge hobby and open-source projects. We make money by charging for higher usage volume and enterprise features like user permissions and support. Give it a spin: https://github.com/replexica/replexica. Let us know what you think!
1 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.