You are browsing as a guest. Sign up (or log in) to start making projects!

luannzin

@luannzin

Joined June 25th, 2026

  • 11Devlogs
  • 3Projects
  • 2Ships
  • 15Votes
Ship

I am currently shipping my stable website version, there is lefting experiences page yet, but i think that peoples can see my work and maybe, star my project, that will help me to continue evolving my personal website.

I did my personal website focusing on internationalization and good UI.

Try project → See source code →
Open comments for this post

1h 29m 15s logged

I did hard changes to the project core

improved the DX based on real projects
improved the README

added a new init script to the library too

0
0
3
Open comments for this post

25m 4s logged

debugging…

i have a bug with my better-intl library that causes client components to re render after detect another locale diff from the defaultLocale

0
0
1
Open comments for this post

2h 2m 14s logged

2hours of work, and i did the initial version of website

it includes Github contributions heatmap, includes projects + blog (no structure of blog yet)

the next steps:

internationalization
blog
projects
experience

everything is in one single page actually, i will improve that soon.

0
0
4
Ship Changes requested

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

  • 3 devlogs
  • 3h
Try project → See source code →
Open comments for this post

1h 50m 56s logged

I changed the package to better-intl

I uploaded the stable version

If you can, star our repo for a better intl pattern in future next.js projects.

Thank you.

0
0
5

Followers

Loading…