How to Internationalize Routing Levels

[semmywong]

How to Internationalize Routing Levels? (eg next-intl in the nextjs )(eg /zh-CN/news/$id and /en-US/news/$id) and default will not show the locale symbol

[sd44]

https://inlang.com/m/gerre34r/library-inlang-paraglideJs/other-frameworks
https://inlang.com/m/gerre34r/library-inlang-paraglideJs/vite

[semmywong]

@sd44 Is it best practice to use the paraglide.js framework in the tanstack start? I somewhat dislike using the paraglide.js library.

[semmywong]

There are no officially recommended internationalization libraries or examples in TanStack Start.

[dotnize]

There was a community member who set up an example here:

https://github.com/IgorSzymanski/tanstack-start-paraglide

So far I don't think I've seen other options besides Paraglide

[semmywong]

There was a community member who set up an example here:

https://github.com/IgorSzymanski/tanstack-start-paraglide

So far I don't think I've seen other options besides Paraglide

@dotnize Would you consider integrating paraglide.js or other i18n libraries like next-intl, react-i18next, or react-intl into the react-tanstarter ?

[MarkForLoop]

In our project, we use paraglide.js
Would recommend

[dotnize]

@dotnize Would you consider integrating paraglide.js or other i18n libraries like next-intl, react-i18next, or react-intl into the react-tanstarter ?

Probably no, or at least not now, sorry

This upcoming feature might help with what you want to achieve:

• feat: optional path params TanStack/router#4597

[semmywong]

In our project, we use paraglide.js Would recommend

@MarkForLoop paraglide.js automatically generates a bunch of JS files based on message keys, which is really annoying. Worse still, it creates one JS file per key, resulting in an excessive number of JS files.