Ask your question and get a summary of the document by referencing this page and the AI provider of your choice
Version History
- "Init history"v9.0.013/06/2026
The content of this page was translated using an AI.
See the last version of the original content in EnglishIf you have an idea for improving this documentation, please feel free to contribute by submitting a pull request on GitHub.
GitHub link to the documentationCopy doc Markdown to clipboard
Migrate from Transloco to Intlayer
If your Angular application currently uses @jsverse/transloco, you can migrate to Intlayer using our compat adapter. This transition allows you to maintain your existing template syntax while utilizing Intlayer's powerful dictionary structure.
What to do
Simply run the initialization command in your project:
Copy the code to the clipboard
npx intlayer initThis will generate the necessary intlayer.config.ts configuration. You will then replace your Transloco imports with @intlayer/transloco modules or rely on the build aliases.
What it does under the hood
Transloco uses scopes and a TranslocoService (translate, selectTranslate), alongside structural directives (*transloco="let t") and pipes (| transloco).
Under the hood:
- Scopes: Map naturally to Intlayer dictionary keys, providing a great pruning story for bundle optimization.
- Service & Directives: Intlayer's Angular adapter seamlessly replaces the providers, allowing your existing template pipes and directives to resolve strings against Intlayer dictionaries.
- Build time parsing: The TypeScript analyzer recognizes
instant/getcalls, and fallback pruning ensures correctness even when template usage isn't statically trackable.