Our great sponsors
-
typesafe-i18n
A fully type-safe and lightweight internationalization library for all your TypeScript and JavaScript projects.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
typesafe-i18n-demo-sveltekit-jsdoc
A small project demonstrating a `typesafe-i18n` integration with SvelteKit
As for your i18n solution, I'd say sourceLanguage. But as a developer, I'll always code in en and as a SvelteKit user, I'll probably use this library until official support on this topic from SvelteKit arrives.
Before wasting anyone's time, I want to say that I searched on the web about this topic and I wasn't able to come up with a full solution. I guess that - at least - I narrowed down my doubts (horray!). I am aware that this topic is opinionated, so any help here would be.... very helpful.
So, the question, is the following: how should handle routing in an internationalized app? Consider that I've explored the above library example, so I'll narrow my question a little; considering SEO AND UX/UI, should I: