Hey, looks like a great start. Soe comments:

1. Please merge from main. There's a large change in Login flow
2. I think we don't need the React library. It seems like you can just initialize the i18next and use it (we might not need the cache of the react-i18next / next-i18next. Please let me know if I'm missing something.
3. Please use the translations in the .json file, import, and import it.

TIA

@gemanor yes, this branch is up to date with main branch please review this PR

Hey @techmannih, your PR is missing many strings in the components / lib folder. It also has many styling issues (run npm run test / npm run lint to find them).
Please address them in the next 48 hours, as we want to close this PR and already have some others waiting.

@gemanor please review now

@techmannih seems like the lint/prettier is still failing (see the CI tests..)

Hey @techmannih , all the tests are passing now on main
Please merge from main and ensure all the tests is passing

@gemanor I am able to see any command in components / lib. can you help me to show

@gemanor now all test pass, please check

Hey @techmannih, there are many strings in the components/hooks folders that are still not included in the i18n support. Please make sure you include them too..

Tests are good now indeed :)

@gemanor these are not command string there are only error and text string, I think we are fixing command string, please confirm, if I am correct

Hey @techmannih, there are many strings in the components/hooks folders that are still not included in the i18n support. Please make sure you include them too..

It should be on all strings. Actually, everything in the components is something that renders as part of the commands. The command folder is only the high-level component of the commands