// the find
generaltranslation/gt
Full-stack localization for every framework
A monorepo of i18n packages for React/Next.js/Vue that translates whole JSX components via a <T> wrapper instead of making you refactor strings into key-based dictionaries. Comes with a CLI, bundler plugins (webpack/Vite/Rollup/esbuild), an ESLint plugin, and an AI agent (Locadex) meant to auto-wire i18n into an existing codebase. Aimed at teams who want to add translation without doing the usual dictionary-extraction grind.
The <T>-wrapper model is a real architectural difference from react-i18next/next-intl, not just another API shape — translating JSX trees instead of extracted strings is a genuinely different bet. Broad surface: separate packages for Next.js, plain React, and Vue, plus compiler plugins across four bundlers, so it's not locked to one meta-framework. The repo shows actual engineering process — changesets, a benchmark CI workflow, a dedicated ESLint plugin for linting the React core integration, and a nightly locale-switch test against next@latest.
The whole workflow assumes a hosted API key from generaltranslation.com — the README never mentions self-hosting or an offline translation path, so you're trusting a third-party service with your UI copy and paying (or rate-limited) by default. The README is pure marketing copy with zero actual code — no sample of what a <T>-wrapped component looks like, so you can't evaluate the core claim without leaving the repo. Wrapping components rather than extracting strings is invasive at scale and the README says nothing about how it handles pluralization, interpolation, or SSR/hydration mismatches, which is exactly where component-level translation schemes tend to break. Locadex, the flagship 'AI agent does your i18n for you' pitch, routes through their dashboard/GitHub integration — another layer of vendor dependency for something that should be a dev-time concern.