--- title: Translations in Angular enterprise application with i18next description: A guide on handling translations in an enterprise Angular application using i18next. The setup is built on an NX-managed monorepo with vertical slicing... canonical: https://daily.dev/posts/translations-in-angular-enterprise-application-with-i18next-yqzqmbvo9 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Translations in Angular enterprise application with i18next | daily.dev og:description: A guide on handling translations in an enterprise Angular application using i18next. The setup is built on an NX-managed monorepo with vertical slicing... og:url: https://daily.dev/posts/translations-in-angular-enterprise-application-with-i18next-yqzqmbvo9 og:image: https://api.daily.dev/og/posts/YqZqMBVo9.png og:image:alt: Translations in Angular enterprise application with i18next og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Translations in Angular enterprise application with i18next **[Giorgio](https://daily.dev/sources/butlunyzqzvbnmjntq8pw)** · [@giogdev](https://daily.dev/giogdev) · 1 min read · 0 upvotes · 0 comments ## Summary A guide on handling translations in an enterprise Angular application using i18next. The setup is built on an NX-managed monorepo with vertical slicing architecture, and focuses on lazy, fragmented loading of translation files per application domain. This approach avoids downloading a single large translation bundle on initial load, improving performance and Core Web Vitals. ## Content **When an application needs to support multiple languages, it's best to plan translation handling from the very start,** instead of scrambling to patch things up once development is already started. In today's post I want to share how I handled translations in an enterprise Angular application. We'll start from the application's architecture (**spoiler: an NX-managed monorepo, organized with vertical slicing**) and work our way to lazy loading the translations for each individual application domain. Lazy, fragmented translation loading with i18next matters a lot, especially for enterprise applications. The alternative would be downloading one huge definitions file on initial load, which causes needless slowdowns and hurts your Core Web Vitals. 🇬🇧 [https://www.thinkasadev.com/en/translations-angular-app/↗](https://www.thinkasadev.com/en/translations-angular-app/) 🇮🇹 [https://www.thinkasadev.com/traduzioni-in-app-angular-enterprise/↗](https://www.thinkasadev.com/traduzioni-in-app-angular-enterprise/) ## Similar posts on daily.dev - [Enabling internationalization in our web Turbo monorepo](https://daily.dev/posts/enabling-internationalization-in-our-web-turbo-monorepo-cz52gwlcb) · Mercari Engineering · 2 upvotes · 0 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#angular](https://daily.dev/tags/angular) [View this post on daily.dev](https://daily.dev/posts/translations-in-angular-enterprise-application-with-i18next-yqzqmbvo9) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/translations-in-angular-enterprise-application-with-i18next-yqzqmbvo9","headline":"Translations in Angular enterprise application with i18next","text":"A guide on handling translations in an enterprise Angular application using i18next. The setup is built on an NX-managed monorepo with vertical slicing architecture, and focuses on lazy, fragmented loading of translation files per application domain. This approach avoids downloading a single large translation bundle on initial load, improving performance and Core Web Vitals.","url":"https://daily.dev/posts/translations-in-angular-enterprise-application-with-i18next-yqzqmbvo9","datePublished":"2026-06-16T06:49:55.449Z","dateModified":"2026-06-16T06:50:20.581Z","author":{"@type":"Person","name":"Giorgio","url":"https://daily.dev/giogdev","image":"https://media.daily.dev/image/upload/s--VzsFQRBX--/f_auto/v1742975876/avatars/avatar_bUTlUNyzqZVBNMJnTQ8PW","description":"Hi, I'm Giorgio!\nI work as software developer and I love everything is nerd! ","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":210}},"image":"https://media.daily.dev/image/upload/s--0d5reCWL--/f_auto/v1781592595/posts/YqZqMBVo9?_a=BAMAMiWQ0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/butlunyzqzvbnmjntq8pw","name":"Giorgio"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Giorgio","item":"https://daily.dev/sources/butlunyzqzvbnmjntq8pw"},{"@type":"ListItem","position":3,"name":"Translations in Angular enterprise application with i18next"}]} ```