Feat/add translation support

[Klhmt]

First implementation of the translation mechanism.

How translate things in the code

• add translation in the code (either with the React component or with the macro)
• run pnpm run extract
• add the translation on the messages.ts files in src/locales/*/
• run pnpm run compile EDIT: done by the Vite plugin

I think there's room for improvements (maybe make the list of supported languages dynamic based on the existant files in locales/*...)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
fluorite	Ready	Preview	Comment	Sep 22, 2025 2:39pm

[AFCMS]

• Fix the current ESLint issues
• Consider adding Lingui ESLint plugin: https://lingui.dev/ref/eslint-plugin
• Add new NPM scripts documentations to both README and Copilot instructions
  • https://github.com/AFCMS/fluorite/blob/master/README.md
  • https://github.com/AFCMS/fluorite/blob/master/.github/copilot-instructions.md

I didn't test the code yet.

About the translations and auto generated files, I think we should bring a pre-commit library like Husky to run the translation update before committing (in another PR).

[AFCMS]

Not a problem here but argggg forced to use babel here.

If the React parser was SWC it could have use the SWC plugin instead (much faster).

Here most of the React work is made by OXC which is faster than SWC, but still rely on Babel for the React compiler, and now the Lingui plugin 😢

I want more Rust in the web 🦀

[Klhmt]

lingui/js-lingui#2283

[AFCMS]

Is there a reason to use <Trans> instead of t here?

We do not plan on adding nested JSX components under it at the moment.

[Klhmt]

See https://lingui.dev/tutorials/react#macros-vs-components for the difference. At compilation the macros are transformed into <Trans>. I'll use a macro there to be more consistant

[AFCMS]

It's not the goal of the PR here but in the short term we should have a configuration page with app language and not solely rely on the browser language.

I think we should either bring a component library or build our own but it require some brainstorming first.

In general I think we should aim at a very minimalistic UI and a settings page will quickly become a requirement (don't want a big dropdown in the control bar).

[AFCMS]

Conflicts 😬

There is one new string in ControlBar.tsx, fix the conflict in package.json then delete and pnpm install to recreate pnpm-lock.yaml.

Should be pretty easy to fix the tsconfig.