... Hello PH community ! My colleague Marine recently needed to go multilingual fast and she really didn t feel like going through the usual i18next boilerplate again. She ended up trying @Intlayer , which lets you co-locate translations right next to your components - no JSON files, no string keys, and fully type-safe. It felt super clean for small projects, but now we re curious: What i18n setup are you using in 2025? Any tools or patterns you d recommend ...

... aymeric_pineau , we kept asking ourselves that question. We were looking for a simple, scalable, and developer-first solution for handling multilingual content in our projects, and couldn't find exactly what we needed. So we built our solution : @Intlayer . Intlayer

... past few weeks. We ve been struggling with i18n for a while. Not the translations themselves, the process. The context switching. The messy workflows. The disconnect from the code. So we built a small open-source tool to help: Intlayer MCP Server, a local server that lives in your IDE to manage multilingual content without breaking your flow. It s nothing fancy. Just a way to stay in dev mode while making your app global ready. No dashboard. No external ... ... your editor. Still early, still raw. But we figured some of you might vibe with it. Thanks to the VibeCoding crew for the inspiration and the mindset. Less friction. More flow. That s the goal. Check it out : https://intlayer.org

... vibe coders! Today, I just want to share our new free tool we use, for all SaaS builders who deal with translation files and multilingual content : Intlayer Autofill . The Problem: If you're building a growing SaaS, you've probably hit this wall: You're splitting content into reusable components. You're updating translations manually every time something changes. And you're juggling multiple tools and locales just to keep everything in sync. It s messy. It s slow ... ... doesn t scale. The Fix: Intlayer