npx i18next-cli instrument

Internationalizing a React application used to mean a tedious weekend of hunting down every hardcoded string, manually wrapping each one in a t() call, injecting useTranslation() hooks into every component, and praying you didn't miss a corner case. The reality is that most apps ship without i18n simply because the upfront cost feels too high. The new instrument command in i18next-cli changes that equation entirely. In this post, we'll take a React + Vite + TypeScript project — Taskly — from zero i18n to a cloud-synced, multi-language application in just a few steps. The Starting Point: A Standard React App Taskly is a typical modern project: Vite, React, and TypeScript. It has no i18n dependencies and no translation files—just English strings scattered throughout the JSX: // DashboardPage.tsx (before) < h1 > Here's your overview </ h1 > < p > You have { activeCount } tasks left to complete. </ p > This is the "Before" state. Let's start the transformation. Step 1 — Instrument: Let the