Show HN: A simpler way to manage internationalization in component-based apps
4 MarineCG40 5 8/27/2025, 4:26:03 PM github.com ↗
I built this because I was frustrated with how messy translation files get as projects scale.
Most i18n solutions force you to manage big JSON dictionaries, spread across multiple files, and then manually wire everything into your UI. It quickly becomes hard to keep things organized, especially in component-heavy apps.
This approach is component-first i18n: translations live close to the UI they belong to. That makes it easier to keep things organized, avoid duplication, and scale without the usual chaos of string management.
It’s lightweight, works with React/Next.js, and is designed to stay simple while your app grows.
Comments (5)
aurelb · 2h ago
I love this approach! Really clean and straightforward
MarineCG40 · 2h ago
Reach me out if you implement it
hermoine39039 · 2h ago
Interesting solution. Would love to try it.
MarineCG40 · 2h ago
Tell me more when you try it !
john_wick321 · 2h ago
“Nice — the JSON mess in i18n has bitten me more than once. Keeping translations local to components seems way saner.”