{"id":84321,"date":"2024-06-10T10:59:00","date_gmt":"2024-06-10T08:59:00","guid":{"rendered":"https:\/\/phrase.com\/?p=84321"},"modified":"2024-06-07T16:00:29","modified_gmt":"2024-06-07T14:00:29","slug":"nestjs-localization","status":"publish","type":"post","link":"https:\/\/phrase.com\/blog\/posts\/nestjs-localization\/","title":{"rendered":"A Guide to NestJS Localization"},"content":{"rendered":"\n
\n\n\t\n\t
\n\t\t
\n\t\t\t<\/h2>\n

A fast and loose framework like Express is great for small server-side apps, but as projects and teams scale, clean architecture and patterns are needed to keep things SOLID<\/a>, making it easier to find and change code. Enter the Angular-inspired, architecture-focused NestJS<\/a>, which sees downloads of 3 million per week<\/a>. The thoughtful structure of NestJS facilitates our projects\u2019 growth while minimizing technical debt.<\/p>\n

While NestJS is a comprehensive framework, it leaves internationalization (i18n) up to the developer. Fortunately, Toon van Strijp<\/a> created nestjs-i18n<\/a>, a library that greatly simplifies NestJS localization. nestjs-i18n<\/code> resolves the current request\u2019s language, manages translation files, and formats messages, all with built-in type safety. In this guide we\u2019ll take nestjs-i18n<\/code> for a spin, building a REST API with NestJS and localizing it. Let\u2019s dive in.<\/p>\n

\ud83d\udd17 Resource<\/strong> \u00bb<\/strong>\u00a0Internationalization (i18n) and localization (l10n) allow us to make our apps available in different languages and regions, often for more profit. If you\u2019re new to i18n and l10n, check out our guide to internationalization<\/a>.<\/p>\n

\ud83d\udd17 Resource<\/strong> \u00bb<\/strong>\u00a0If you\u2019re interested in general Node.js or Express i18n, check out our Guide to Node.js Internationalization (I18n)<\/a>.<\/p>\n

\n
\n

Overview<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n