next-intl
next-translate
Our great sponsors
next-intl | next-translate | |
---|---|---|
5 | 11 | |
1,678 | 2,514 | |
- | 1.1% | |
9.6 | 7.9 | |
8 days ago | 7 days ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
next-intl
- How next-intl Works
-
Localized tRPC errors
We start with a project that was bootstrapped with create-t3-app. For internationalization we use next-intl and set it up as described in the getting started guide. With this initial project setup we can jump into implementing localized error messages.
-
Translating zod errors with next-intl
When starting a new project with Next.js these days, next-intl and zod are my go to libraries for internationalization and schema validation, respectively. Of course, when using zod for client-facing validations I would like to translate potential error messages. The package zod-i18n can be used to achieve this for i18next, a popular alternative internationalization library. This means that by using this library as starting point one can quickly achieve zod translation with next-intl.
-
Next.js internationalization (i18n) tutorial
As we mentioned earlier, the Next.js works well with existing i18n libraries (react-intl, lingui, next-intl, and similar). In this tutorial, we will use the react-intl.
-
i18n and Next.js
next-intl
next-translate
-
Next.js Weekly #34: StyleX, Self-Healing URLs, AuthKit, Scaleable TailwindCSS, Layouts vs Templates, Faster Next.js Websites [👇 all links in the comments]
next-translate
-
🏝️ i18n translations in Next.js 13's app-dir for server/client components 🌊
Next-translate repo: https://github.com/aralroca/next-translate
-
Translate NextJS website
My team was using next-i18next, but switched to https://github.com/vinissimus/next-translate because we use getInitialProps
-
React 16.14.0: Error was not caught ReferenceError: exports is not defined
I'm the author of next-translate library, and I'm working on an experimental version to which I get an error with React 16.14.0 and I don't understand why it happens. Upgrading React to version 17 then it works fine, but I don't want to force everyone who uses the new version of my library to migrate their React version.
-
How to translate NextJS application with next-translate?
NextJS, as a very popular framework among React programmers, offers a variety of features and external libraries, that create a very developer-friendly environment. One of them is next-translate, a translation library that well known for its simple set up and use. In this blog post, you will learn to configure next-translate in your NextJS app, and to manage translations with SimpleLocalize assist.
-
Top 12 libraries for NextJS, React apps and React Native apps for i18n and react localization
9. next-translate
What are some alternatives?
next-i18next - The easiest way to translate your NextJs apps.
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
react-i18next - Internationalization for react done right. Using the i18next i18n ecosystem.
nextjs-multi-domain-locale - Hosting multiple domains on the same Next.js site (while maintaining multiple languages and SSG)
react-i18nify - Simple i18n translation and localization components and helpers for React.
nestjs-localization - Nestjs localization provides a convenient way to retrieve strings in various languages, allowing you to easily support multiple languages within your application.
react-native-localize - 🌍 A toolbox for your React Native app localization
react-intl-hooks - React hooks for internationalization without the hassle ⚛️🌍
awesome-i18n - 🌍 A curated list of i18n resources for all kind of languages and frameworks
nextjs-i18n-example - Next.js internationalization with react-intl