Best practices in SvelteKit for i18n / L10n / internationalization / localization?

[rosano]

I've seen the issues for brainstorming and translations, and would like to know: is there a recommended approach until the built-in solution is released?

Some solutions I've seen include:

• svelte-i18n usage with SvelteKit
• typesafe-i18n integration with SvelteKit
• implementation for sveltevietnam.dev

[anthumchris]

I tried researching this today and couldn't find international language support in the SvelteKit FAQ nor search results below:

• https://kit.svelte.dev/search?q=i11n
• https://kit.svelte.dev/search?q=internationalization
• https://kit.svelte.dev/search?q=language
• https://kit.svelte.dev/search?q=locale

Related:

• Add a page on Internationalization to the docs #12160
• Solve SvelteKit Limitations for performance and i18n #12001 mentions a i18n limitation, but no implementation method was detailed.

[mobilars]

Would be great to know if there is some official support for multiple languages planned, so that we don't go for one solution and then Sveltekit comes with a new solution that's better long term.

[vnphanquang]

Maintainer of sveltevietnam.dev here. Just want to say that over the years, our i18n implementation has gone through some major iterations, the latest of which now leverages Async Svelte and Remote Function from SvelteKit.

The solution is packaged as @sveltevietnam/i18n. A complementary blog post about it is at "Internationalisation with Remote Function — A Proof of Concept".

There is also wuchale and paraglide, each with its own merits and gotchas.

I do also believe that first party support should be realised at some point in the future.