Add Transloco to external component library.

[TomRaaff]

Is there an existing issue for this?

• I have searched the existing issues

Which Transloco package(s) will this feature affect?

Transloco

Is your feature request related to a problem? Please describe

So far I've seen implementations for Transloco and shared translations in libs within a mono-repo. However, we don't have a mono-repo, but a MainProject that depends on a ComponentLibrary. I want to use Transloco in both. I've added Transloco to the MainProject without issue. However, when I add it to the ComponentLibrary, I get problems due to having two HttpClient instances. (The ComponentLib needed an HttpClient so it could fetch the translationsfile).

Besides that, I forsee some other problems:

• If I have two HttpClients, I'll have two TranslocoServices as well
• with two TranslocoServices, the changing of language will be executed by only 1 of them.
• How do I manage my translations? Can I add translationfiles to the library or does the MainProject need to contain the translations for the library as well?

Describe the solution you'd like

Documentation on how to add Transloco to an external library

Describe alternatives you've considered

No response

Describe alternatives you've considered

Implementing our project as a mono-repo, but that is not an option.

Describe alternatives you've considered

Expected behaviour: I expect transloco to be usable among multiple projects/libraries and for there to be a way to easily maintain the translations

Additional context

No response

I would like to make a pull request for this feature

No

[Serrulien]

Hello,

I'm maintaining a project similar to yours. However the library doesn't fetch its translation files by itself, the consumer of the library must do it.

The translation files of the library are bundled into its dist folder then transloco-scoped-libs will help you to extract them on the consumer side.

Read https://ngneat.github.io/transloco/docs/tools/scope-lib-extractor/ to know how to do it.

This strategy is useful when both consumer and libraries use transloco.