aymericzip

@AyrlonnGalvao It’s definitely still an open debate. But 90% of projects still add i18n later on anyway Today, most solutions provide extractors to generate the json, and those not backed by Crowdin include auto-translation features too. That really helps speed up the refactoring

i18n desde o dia 1 — não depois Adicionar internacionalização em projeto existente é caro. No RotaLabs: /br, /en, /es desde o scaffold inicial. hreflang correto. Slugs de locale definidos como imutáveis. O mercado em inglês é 10x maior. O mercado em espanhol é quase tão grande quanto o brasileiro. Custo de fazer certo agora: algumas horas. Custo de refatorar depois: semanas.

Quando você constrói um produto sozinho, cada escolha técnica tem peso diferente. Não tem time para absorver dívida técnica. Não tem eng. sênior para refatorar depois. Por isso cada decisão no RotaLabs foi pensada para durar — não para impressionar. Thread sobre as escolhas que fiz e por quê. 🧵

@ishratn00ri The flow I actually use is: 1 - Ask Claude to develop the feature without i18n 2 - Run the extract command with Husky 3 - Fill translations in GH Action Then, keeping multilingual content outside the components helps avoid token explosion when Claude continues the work

@aymericzip The component level approach is actually interesting tho

React devs, do y’all actually use i18n in production apps?

@docsbook @Intlayer_org Happy to take your recommendations for improving the docs 👀

@Intlayer_org intlayer is a genuinely useful tool — impressed by how well it's put together. The only thing that undercuts it: documentation that doesn't look like it belongs to the same product. Made a hosted docs page with full branding support — logo, theme, custom domain. Go take a look.

Intlayer 8.10.0 is now live 🚀 You can now declare content directly using: - .content.md - .content.yaml Perfect for: - blogs - documentation - privacy policies - long-form content These files are fully editable from the Visual Editor ✍️

@maz225 What you’re describing is exactly what the Intlayer compiler was built for. Other solutions like Wuchale or Lingodev claim to support it as well, but from what I’ve tried, they just didn’t work as expected

@aymericzip hmmm.. not exactly what I was looking for.. but thank you 🙏 i was looking for something you just init it in a plugin with the current locale and the locales you need and you add a button to switch locales, then it automatically translates text and does everything.. idk..

is there any thing better than i18n for multilingual sites? 😅 it's awkward.. why do i need to edit json files for every text i add + make sure all the json structure is identical for every locale + the weird t("home.hero.title") thing there HAVE to be some alternative out there

@___walkalone You can have a look to intlayer intlayer.org/doc/environmen…

あの、、、ちょっと気になるんですけど、Astro.js使ってる方に聞きたいのが、astro.config.jsにインテグレーションを読み込むだけで、多言語対応できるライブラリがあったらそれって需要あるかな

@Jabelic_ It's great, I like it. It reminds me of the first version of Intlayer, when I used to recommend using useDictionary. I thought the unused translations would be purged, but I never found a solution, so I had to move to that approach.

Im developing an i18n library for App Router called "i18n-at". Please do give it a try. npmx.dev/package/i18n-at #i18n

@alexisbchz I tried implementing that feature from @alexisbchz The implementation seems just ok enough from my point of view, but I still think it’s a useful feature for large corp

The world would be a better place if every website had this. ui.alexisbouchez.com/ovh/marketing/…

@r_marked @ay_ushr @dominikkoch @theo @lingodotdev Just reworked the experience on mobile, thanks @r_marked

@aymericzip @ay_ushr @dominikkoch @theo @lingodotdev You should just block access on mobile because it’s completely unreadable/navigable.

Hi @theo @r_marked (happy birthday btw) is there any chance t3chat ever gets translated to more than just english? I want to get my dad on t3chat but he would prefer german ui More than happy to translate the whole app for free!

@schanuelmiller @melvynx Another thing, for i18n needs: The {-$locale} segment means transforming all the app to adapt all links, etc I would love to see an prefix injection at the root router level see discussion github.com/TanStack/route…

@aymericzip @melvynx why that distinction? what's missing for you in TanStack Start?

I try to migrate my app from Next.js to Tanstack Start : build time is literally divided by 2

@schanuelmiller @melvynx Page rendered → loading → page rendered → loading → page rendered. The data is retrieved with `const { project } = Route.useLoaderData();` It should be a static page, so there’s no reason for the `defaultPendingComponent` to appear here

@aymericzip @melvynx what's a "flip" ?

@schanuelmiller @melvynx I just mean, I assume that tree shaking, bundling, minification, crawling, and prerendering are operations that can make the build slower. And I’m okay with waiting one more minute if the final app is lighter and more performant

@aymericzip @melvynx we are working on an API for providing those params. what does "if it tree shake more efficiently" mean here?

@melvynx For SaaS / Dashboard -> tanstack is much better docs / blogs / landing page -> nextjs is still the way to go for me

@aymericzip ?

@melvynx I tried migrating the Intlayer docs from nextjs to tanstack, but pre-rendering ended up taking twice as long as with nextjs. I also ran into flip and hydration issues. Something may have been wrong with my setup, but I ended up sticking with nextjs for that app

@r_marked @ay_ushr @dominikkoch @theo @lingodotdev I agree, but it’s also a good way to kill Google positioning Btw, an interesting point I realized about the solutions listed is: the worse the landing page of the solution is, better the tech behind the solution tends to be One example: next-translate from @aralroca

@aymericzip @ay_ushr @dominikkoch @theo @lingodotdev I am a big fan of either making mobile sites work, or admitting they don't and telling the user to use a desktop. any middle ground tends to suck :/