escape-string-regexp VS i18next

escape-string-regexp

We haven't tracked posts mentioning escape-string-regexp yet.
Tracking mentions began in Dec 2020.

i18next

• Show HN: Internationalizationext selector API – selector t for TypeScript
  1 project | news.ycombinator.com | 20 Aug 2025

  i18next.t($ => $.my.nested.key)

  The change unlocks IDE autocompletion and “go to definition”, preserves JSDoc from your resource files at the call site, and — critically — removes the huge type-level unions that used to grind TypeScript/IDEs to a halt. See the announcement and examples.

  The selector support has landed in i18next (PR merged) and react-i18next has matching typings/changes. If you want to migrate, there’s an automated codemod to convert usages to the selector form.

  Why share this here: if you use TypeScript + i18next, this should make working with large translation catalogs far more pleasant — less “doom scrolling”, much better editor UX, and big type-performance improvements. We’d love feedback from folks who try the codemod or hit edge cases. => https://github.com/i18next/i18next/pull/2322

• How to Implement Translations in a React App Using TypeScript?
  1 project | dev.to | 13 May 2025

  The first step to implementing translations in a React app is to choose an appropriate library. One of the most popular libraries in the React ecosystem is i18next, which provides powerful features for internationalization. It allows you to easily manage translations, plural forms, and formatting.

• Building a Scalable i18n System in React
  4 projects | dev.to | 2 May 2025

  This approach works particularly well for growing applications, allowing team members to work on different features without conflicts. For more information, check out the documentation for react-i18next, i18next, and js-cookie.

• How to Easily Add Internationalization (i18n) to Your New Software Project
  2 projects | dev.to | 3 Mar 2025

  import i18n from 'i18next' import { initReactI18next } from 'react-i18next' import LanguageDetector from 'i18next-browser-languageDetector' import LocizeBackend from 'i18next-locize-backend' import LastUsed from 'locize-lastused' import { locizePlugin } from 'locize' const isDev = import.meta.env.DEV const locizeOptions = { projectId: import.meta.env.VITE_LOCIZE_PROJECTID, apiKey: import.meta.env.VITE_LOCIZE_APIKEY // // YOU should not expose your apps API key to production!!! } if (isDev) { // locize-lastused // sets a timestamp of last access on every translation segment on locize // -> safely remove the ones not being touched for weeks/months // https://github.com/locize/locize-lastused i18n.use(LastUsed) } i18n // i18next-locize-backend // loads translations from your project, saves new keys to it (saveMissing: true) // https://github.com/locize/i18next-locize-backend .use(LocizeBackend) // detect user language // learn more: https://github.com/i18next/i18next-browser-languageDetector .use(LanguageDetector) // Bind i18next to React .use(initReactI18next) // InContext Editor of locize .use(locizePlugin) // init i18next // for all options read: https://www.i18next.com/overview/configuration-options .init({ debug: isDev, // Enable logging for development fallbackLng: 'en', // Default language backend: locizeOptions, locizeLastUsed: locizeOptions, saveMissing: isDev // you should not use saveMissing in production }) export default i18n In src/main.tsx, import the i18n.ts configuration before rendering the app:

• A Practical Guide to Translating & Localizing Your Web App: Using i18n and Lingo.dev
  2 projects | dev.to | 28 Feb 2025

  In this section, we will translate our previous web page to French and Spanish. The first step to achieve this is to install the i18next and react-i18next packages. i18next is an internationalization framework that makes localization possible for JavaScript, and react-i18next is specifically for React.

• Testing with Playwright: Use i18next Translations in Tests, but not `t('key')`
  2 projects | dev.to | 5 Jan 2025

  E2E-testing localized applications can be challenging, translations keys can make test code harder to read and maintain. This article demonstrates how to test i18next translations in React app using Playwright, with a simplified approach that avoids translation keys. The idea can be used in any project with i18next or similar libraries.

• Roadmap for Next.js
  1 project | dev.to | 12 Dec 2024

  Next.js Internationalized Routing Next.js provides built-in support for internationalized routing. This page will introduce you to the fundamental concepts of i18n routing in Next.js and how to handle it. More Info i18next A popular library for internationalization that provides a complete set of tools for handling translation, formatting, and routing for i18n. More Info

• Advanced Frontend Resources for Next.js Development 🚀
  4 projects | dev.to | 8 Sep 2024

  🌍 i18next Documentation

• How to Easily Add Translations to Your React Apps with i18next
  1 project | dev.to | 15 Jun 2024

  i18next is a popular internationalization library for JavaScript applications. It provides a robust framework for managing translations, formatting dates, numbers, and handling pluralization. i18next supports multiple backends for storing translations, making it versatile and adaptable to various project requirements.

• Implementing Internationalization (i18n) in Vue.js Projects
  1 project | dev.to | 30 Apr 2024

  For this article, we'll leverage the 'Simple CRM' project from our previous list of projects. We'll integrate and utilize the i18n library to internationalize our application.