News for hackers. Stuff that matters.

Show HN: A simpler way to manage internationalization in component-based apps

https://github.com/aymericzip/intlayer

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.
( 6 comments | 4 points | on HN )
Re:Show HN: A simpler way to manage internationalization in ... by aurelb on Wednesday August 27, 2025 @12:33PM (#45041866)
I love this approach! Really clean and straightforward
Re:Show HN: A simpler way to manage internationalization in ... by MarineCG40 on Wednesday August 27, 2025 @12:34PM (#45041874)
Reach me out if you implement it
Re:Show HN: A simpler way to manage internationalization in ... by hermoine39039 on Wednesday August 27, 2025 @12:29PM (#45041818)
Interesting solution. Would love to try it.
Re:Show HN: A simpler way to manage internationalization in ... by MarineCG40 on Wednesday August 27, 2025 @12:33PM (#45041868)
Tell me more when you try it !
Re:Show HN: A simpler way to manage internationalization in ... by john_wick321 on Wednesday August 27, 2025 @12:52PM (#45042093)
“Nice — the JSON mess in i18n has bitten me more than once. Keeping translations local to components seems way saner.”
Re:Show HN: A simpler way to manage internationalization in ... by mr_sumbuddy on Thursday August 28, 2025 @04:16AM (#45049736)
Nice, This looks super helpful for keeping i18n clean and organized, thanks for sharing!