i18next
jsLingui
Our great sponsors
i18next | jsLingui | |
---|---|---|
60 | 9 | |
7,382 | 4,192 | |
1.2% | 1.4% | |
9.2 | 8.8 | |
4 days ago | 6 days ago | |
JavaScript | TypeScript | |
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.
i18next
-
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.
-
Top 20 Frontend Interview Questions With Answers
The best way to implement internationalization is to use an internationalization framework library, such as i18next. With this kind of library, you can easily handle translations and automatically display your frontend labels in the user's language. The frontend application also needs to be flexible and easily configurable so that its layout can change accordingly, reading from left to right or right to left. CSS allows this with the rtl and ltr CSS direction property.
-
Reactive translation/i18n
For reference, I am using i18next for providing translations, which is configured to use the english message string as a key for the translations and fallback to it if no translation is found in the chosen language. I also use the official svelte-i18next integration. It wraps the i18next object in a Svelte store and, among other things, provides reactivity when the language is changed.
-
Building a multilingual NextJS app using the new app directory
// app/components/BuiltInFormatsDemo.tsx 'use client'; import React from 'react'; import {useTranslation} from '../i18n/client'; import type {LocaleTypes} from '../i18n/settings'; import {useParams} from 'next/navigation'; const BuiltInFormatsDemo = () => { let locale = useParams()?.locale as LocaleTypes; const {t} = useTranslation(locale, 'built-in-demo'); return (
{/* "number": "Number: {{val, number}}", */} {t('number', { val: 123456789.0123, })} p>
{/* "currency": "Currency: {{val, currency}}", */} {t('currency', { val: 123456789.0123, style: 'currency', currency: 'USD', })} p>
{/* "dateTime": "Date/Time: {{val, datetime}}", */} {t('dateTime', { val: new Date(1234567890123), formatParams: { val: { weekday: 'long', year: 'numeric', month: 'long', day: 'numeric', }, }, })} p>
{/* "relativeTime": "Relative Time: {{val, relativetime}}", */} {t('relativeTime', { val: 12, style: 'long', })} p>
{/* "list": "List: {{val, list}}", */} {t('list', { // https://www.i18next.com/translation-function/objects-and-arrays#objects // Check the link for more details on `returnObjects` val: t('weekdays', {returnObjects: true}), })} p> div> ); }; export default BuiltInFormatsDemo;
-
Supercharge Your TypeScript App: Mastering i18next for Type-Safe Translations
As our world becomes increasingly interconnected, the development of web applications that cater to a global audience takes precedence among developers. If you're a TypeScript developer, you're likely acquainted with the advantages of static typing and the assurance it provides in your codebase. When it comes to internationalization (i18n) and localization (l10n), maintaining the same level of type safety becomes crucial. This is precisely where i18next, an influential i18n framework, enters the picture.
-
What is the best way to handle a multi-language site?
I am so sorry for all the people using https://www.i18next.com/ and manually defining string ids. Fuck that. I will never write another message id in my life.
We use https://www.i18next.com/ with JSON files for each language. Works flawless with TypeScript and Jest.
-
The joy, the pride and the burden of maintaining open source
As a maintainer of i18next, an open-source localization library, I can attest that there is nothing quite like the feeling of joy and pride that comes from contributing to the open-source community. Seeing others use and appreciate your work is a feeling like no other. But with great power comes great responsibility, and maintaining an open-source project can sometimes be a heavy burden at times.
-
Mastering Internationalization and Localization in JavaScript: A Comprehensive Guide
i18next - a full-featured i18n library for JavaScript. It gives you the option to separate translations into multiple files and to load them on demand.
-
20 Best Libraries and Tools for React Developers
i18next is a very popular internationalization framework for browsers or any other javascript environment.
jsLingui
-
What is the best way to handle a multi-language site?
https://lingui.dev/ by far.
- We will OSS the NextJs + web3 starter kit
-
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.
-
I want multiple language support for my React project, what's the best way of doing it?
We use LinguiJS on a medium sized project and find it to work really well. Itβs small, supports multiple message formats, has CLI scripts for extracting message ids from source, JS apis, Babel macros, React components and hooks, webpack and snowpack plugins, good pluralization support and much more.
-
Handling i18n the proper way
I really like https://lingui.js.org/. It will create the .json or .po for you. And the component is just π.
-
which solutions do you use for i18n in typescript?
I'm a fan of Lingui. I use it for instant.bible.
-
i18n and Next.js
lingui
What are some alternatives?
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.
polyglot - Give your JavaScript the ability to speak many languages.
Screen-Translator - An Electron.js-based desktop application for automatically translating on-screen text.
deepl-translator - This module provides promised methods for translating text using DeepL Translator (https://www.deepl.com/translator) undocumented API.
MJML - MJML: the only framework that makes responsive-email easy
transloco - π π The internationalization (i18n) library for Angular
aws-lambda-fastify - Insipired by aws-serverless-express to work with Fastify with inject functionality.
i18n-node - Lightweight simple translation module for node.js / express.js with dynamic json storage. Uses common __('...') syntax in app and templates.
babelfish - human friendly i18n for javascript (node.js + browser)