**(Paraglide)** (`@inlang/paraglide-js@2.15.1`):

`Paraglide` offers an innovative, well-thought-out approach.
In the context of a vite+svelte app, the tree-shaking their company advertises work as expected, wich is great.
But in the case of a react + tanstack/start, the tree-shaking did not work as expected, same for next.js. That's say I would be double chechking the usage of paraglide in a svelte and tanstack/start project.
The workflow and DX are also more complex than other options.
Personally I dislike having to regenerate JS files before every push, which creates constant merge conflict risk via PRs. The tool also seems more focused on Vite than on Next.js.
Finally, in comparison with other solutions, Paraglide does not use a store (e.g. Svelte store) to retrieve the current locale to render the content. For each node parsed, it will request the locale from the localStorage / cookie etc. It leads to execution of unnecessary logic that impacts the component reactivity.

- svelte-i18n

that solutions answers all needs for i18n in a svelte project. But as it's the case for i18next or other main i18n solution it's a bit heavy (15kb gzip in comparison with 2.3kb for intlayer once the app bundled).

**(Intlayer)** (`svelte-intlayer@8.7.12`):

I will not personally judge `svelte-intlayer` for objectivity’s sake, since it is my own solution.
