🚀 Feature: Add i18n (Internationalization) Support for Project

[yurimutti]

🔖 Feature description

Add i18n (Internationalization) support to the backend handle multiple languages efficiently for responses, error messages, and dynamic content.

🎤 Why is this feature needed ?

In my use case, the application serves users from different regions, and providing localized responses improves user experience, accessibility, and engagement. For example:

English users should see messages in English.
Spanish users should see messages in Spanish, and so on.

Having backend i18n ensures consistent language support regardless of the client-side setup, especially for error messages and server-rendered content.

✌️ How do you aim to achieve this?

Use an i18n library such as i18next, nestjs-i18n, or a custom implementation to manage translations.
Dynamically detect the user’s language from headers (Accept-Language), tokens, or query parameters.
Load and serve translations based on the detected language.
Fallback to a default language (e.g., English) if no translation is available.

🔄️ Additional Information

No response

👀 Have you spent some time to check if this feature request has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Contributing Guidelines

Are you willing to submit PR?

None

• Backend
• Frontend

[yurimutti]

Look at this library! https://lingui.dev/

We can share locales and use them same tool on node,nextjs,react

[yurimutti]

https://lingui.dev/blog/2024/11/28/announcing-lingui-5.0