Posez votre question et obtenez un résumé du document en referencant cette page et le Provider AI de votre choix
Historique des versions
- "Init history"v9.0.013/06/2026
Le contenu de cette page a été traduit à l'aide d'une IA.
Voir la dernière version du contenu original en anglaisIf 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 NGX-Translate to Intlayer
Migrating your Angular application from ngx-translate to Intlayer is easy with the compat adapter, allowing you to bypass the need to rewrite all your templates.
What to do
Begin by running:
Copier le code dans le presse-papiers
npx intlayer initThis sets up the intlayer.config.ts. Replace your TranslateModule.forRoot() setups and import aliases appropriately to point to @intlayer/ngx-translate.
What it does under the hood
ngx-translate uses TranslateService (instant, get, stream) alongside the {{ 'KEY' | translate:params }} pipe and the [translate] directive.
Under the hood:
- Services:
TranslateServicewrapsgetIntlayerand a locale observable, providing exactly the same methods. - Pipes & Directives: Re-implemented to resolve against Intlayer dictionaries directly.
- Loaders:
TranslateHttpLoadersetups are converted to warning stubs because Intlayer inherently resolves and bundles your dictionaries at build time (or through standard dynamic imports), completely eliminating the need for HTTP loaders.