Show HN: Open-source React library to translate apps without rewriting code

1. lingo.dev

   1 11 5,404 9.9 TypeScript

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

   

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. find-jsx-strings

   2 1 6 - JavaScript

   Find hardcoded strings in jsx/tsx files

   

   I just remembered I built a tool to list all hardcoded strings from a React project in a similar way by parsing the AST.

   https://github.com/benmerckx/find-jsx-strings

4. fbtee-migrate

   3 1 1 2.6 TypeScript

   Discontinued [GET https://api.github.com/repos/f8n-ai/fbtee-migrate: 404 - Not Found // See: https://docs.github.com/rest/repos/repos#get-a-repository]

   

   3. Fun fact: this was made entirely on my phone (~2.5h) while I was walking around Tokyo. Voice prompting + o1-pro. Why? My friend was working on porting fbt to TS and said he was planning to build this. I wanted to one-up him + convince him to start using LLMs =)

   One thing you should be aware of is that for at least Japanese, localization is far from just translating the text. There are lots and lots of Japan-specific cultural nuances you have to take into account for web users and even down to actually just having an entirely different design for your landing page often because those you'll find those just convert better when you know certain things are done that are typically not done for you know non-Japan websites.

   Notta (multi-lingual meeting transcriptions + reports) is a great example if you compare their Japanese [1] and English [2] landing pages.

   Note how drastically different the landing pages are. Furthermore, even linguistically, Japanese remains a challenge for proper context-dependent interpretation. Gemini 2.5 actually likely performs best for this thanks to Shane Gu [3], who's put in tons of work into having it perform well for Japanese (as well as other "tough" languages)

   [0] https://github.com/f8n-ai/fbtee-migrate

5. fluent

   4 12 1,657 4.1 JavaScript

   Fluent — planning, spec and documentation

   

   I think modern Japanese is LTR, but besides that - I believe the project you worked in the past solves an important problem.

   Besides pluralization (and e.g. Arabic having 6 forms zero/one/two/few/many/other), turned out number internationalization and currency conversion are big next challenges the community wants to address next.

   > create ICU compliant JSON.

   I think this is an excellent idea. I have a feeling in the future we will need ICU v2.0, sort of, but unfortunately it's an extremely hard problem and the probability to fail is pretty high (looks like project fluent is not actively maintained anymore: https://github.com/projectfluent/fluent)

6. secure-electron-template

   5 8 1,713 3.7 JavaScript

   The best way to build Electron apps with security in mind.

   

   I solved this in a repository I made a few years back. By switching languages, .missing.json files are generated with the words that don't have the other-language equivalent. Then, you run this script which calls the google translate API to generate the translations. https://github.com/reZach/secure-electron-template/blob/mast...

   Granted, it still suffers that it's not a human translator, but it doesn't require a LLM.

Suggest a related project