We're launching Intlayer v7, an i18n framework that works alongside i18next, react-intl, vue-i18n, and other libraries instead of replacing them. The problem: You're using i18next but want AI translation. Or you need centralized content management but don't want to migrate everything. Or missing translations keep slipping into production because there's no automated testing. Most i18n tools force you to choose their entire ecosystem or nothing. Our approach: Intlayer is a compatibility layer. It sits between your app and your existing i18n library, adding:

Multi-AI provider support (ChatGPT, Claude, DeepSeek, Mistral with your own API keys) CMS integration for externalized content management Automated translation testing in CI/CD (Jest/Vitest compatible) Git-aware tracking that only translates what changed

How it works: The plugin system intercepts your existing i18n library calls to provide additional functionality (content externalization, testing hooks, AI fallbacks) while core translation logic stays in your chosen library. v7 rebuilt the caching system for faster builds, optimized TypeScript generation, and reduced bundle sizes. The integration layer adds minimal overhead, translation lookups pass through to your existing library. Tech stack: Works with React, Next.js, Vue.js, Nuxt.js, Vite. MIT licensed, built in TypeScript. Documentation: https://intlayer.org/doc/releases/v7

Curious about feedback on the compatibility layer architecture and if others have solved similar problems differently.