@luannzin

I built **better-intl**, an internationalization framework for Next.js focused on making i18n feel like a natural part of your project instead of a separate system.

The core idea is simple: translations live next to the components and routes they belong to. Every `t.ts` file is automatically discovered, merged into a fully typed translation object, and statically generated, giving developers autocompletion, type safety, and zero runtime overhead.

The biggest challenge was designing an API that stayed both powerful and intuitive. I wanted to avoid the common pain points of traditional i18n libraries—large JSON files, duplicated keys, complex configuration, and weak TypeScript support—while still supporting nested translations, multiple locales, and build-time generation.

I'm most proud of the developer experience. Developers write translations exactly where they're used, keep every locale together in a single file, and get complete type safety without generating verbose schemas or manually maintaining translation keys. The project feels lightweight while solving a surprisingly complex problem.

To test the project, simply install the package in a Next.js application, create `t.ts` files alongside your routes or components, and run the development server. better-intl automatically discovers and generates the translation tree, so you can immediately access translations through a fully typed API without additional setup.

Repository: https://github.com/luannzin/better-intl

Package: https://www.npmjs.com/package/better-intl