transloco VS core

Some libraries support ways to handle missing translations (e.g., TranslocoMissingHandler from Transloco or MissingTranslationHandler   from ngx-translate). So that's a way to find out any missing translations, but that's quite manual because you have to go over every part of the served application.

For Svelte.. not sure if there's a best package.

[0] https://github.com/ngneat/transloco

Transloco 4.3: ChangeLog

We migrated from ngx-translate to Transloco ~2 years ago and it was quite painless. They have nice migration section for ngx-translate

You can take a look at Transloco. We use it all our projects.

I find Transloco a lot easier to work with compared to lokalize: https://ngneat.github.io/transloco/

I'd recommend https://ngneat.github.io/transloco/

There are a lot of tools available, but many depend on your budget. I personally enjoy Transloco.

ngx-translate is in maintenance mode and won't be develop any further (see https://github.com/ngx-translate/core/issues/783). I would highly recommend to use Transloco instead (https://ngneat.github.io/transloco/). It has same functionality as ngx-translate. Last time I checked ngx-translate doesn't actually lazyLoad translations properly but Transloco does.

Some libraries support ways to handle missing translations (e.g., TranslocoMissingHandler from Transloco or MissingTranslationHandler   from ngx-translate). So that's a way to find out any missing translations, but that's quite manual because you have to go over every part of the served application.

ngx-translate

It was rather painless. We are using ngx-translate which seems dead at this point but works fine in 16 (seems to have gotten a recent commit).

The problem with Angular 15 was the Ivy engine. And it wasn't fixed, maybe you're not affected. https://github.com/ngx-translate/core/issues/1185

He talks about it more here: https://github.com/ngx-translate/core/issues/783

Ngx-translate is not updated anymore. Latest version is a year old. It's still not abandoned but it seems like the developer moved on to work on Angular i18n.

Just to refer to the original docs: https://github.com/ngx-translate/core

One of the common pitfalls when using i18n are large translation files size and inability to split them in order to hide parts of your application from prying eyes. Some solutions like Angular built-in implementation are really powerful and SEO compatible but require a lot of preparation and do not support switching languages on the fly in development mode (which was causing troubles at least in version 9); other solutions like ngx-translate require you to install several packages and still don’t support splitting up a single language.