locize-cli VS next-i18next

Now let's install the locize-cli:

Just use this cli to synchronize the translations with your code. To see how this could look like check out Step 1 in this tutorial.

install the locize-cli (npm i locize-cli)

You can, for example, run an npm script script (or similar), which will use the cli to download the translations from locize into the appropriate folder next-i18next is looking in to (i.e. ./public/locales). This way the translations are bundled in your app and you will not generate any CDN downloads during runtime.

First you need to signup at locize and login. Then create a new project in locize and add your translations. You can add your translations either by importing the individual json files or via API or by using the CLI.

First in locize, create a dedicated version for production. Do not enable auto publish for that version but publish manually or via API or via CLI. Lastly, enable Cache-Control max-age​ for that production version.

internationalization doesn't seem to work out of the box in serverless mode, you may be interested by issue_274, issue_911, issue_1311, issue_1490, issue_1552

About the stack: - Typescript - Nextjs - TailwindCSS - Styled Components - Emotion - Twin.Macro (combining Styled Components with TailwindCSS) - NextI18Next integrated (wrong translationkeys result in compilation errors) - Web3React - Ethers - Redux Toolkit + Redux Observables (with hydration example) - Ramda among others

Choose the correct package or library for React/next i18n, in this case as recommendation use i18next https://www.i18next.com/ and https://github.com/isaachinman/next-i18next for nextJS

NextJS, a well-known framework among React developers, provides multiple libraries that create a very developer-friendly environment. The most popular ones are i18Next, next-translate and, our main focus in this blog post, next-18next, a translation library that does a fantastic job helping in translation management. The following blog post will show you how to set up next-i18n in your NextJS app and manage translations with SimpleLocalize. Take a look at our demo app for the reference.

Now that you have internationalization set up for your Strapi project, it’s time to do the same in your Next.js app. For this part of the tutorial, you’ll be using a library called next-i18next. This library is built on i18next, a popular internationalization framework offering support for many frameworks, like React, Next.js, PHP, and .NET.

2. Instalamos y configuramos next-i18next

Let's take the example of next-i18next. While next-i18next uses i18next and react-i18next under the hood, users of next-i18next simply need to include their translation content as JSON files and don't have to worry about much else.

However, there are a libraries that can help to not reinvent the wheel. In this blog post, we will use next-i18next.

There is https://github.com/isaachinman/next-i18next which basically is like react-i18next but with support for SSR

Let's install the next-i18next library.