How can I use translations outside of components?

[hqw567]

How to use translation outside of components? I have some special circumstances where I need to use translation outside of the component. Is there a compatible method to use translation outside of the component? Although it is troublesome and terrible, I still need to consider this situation.

[nishantbhavasar]

Hello @hqw567,
i have this same type of requirement have you found any solution to use translation outside of the component.

i am working with next.js or i have implement translation both side client side or server side component but i am calling Api's outside my components and need to handle error or other things in multi language
so if you find any solution of this please provide me

Thank you

[hqw567]

@amannn Can you help us out?

[amannn]

Please see https://next-intl-docs.vercel.app/blog/translations-outside-of-react-components

[hqw567]

If I must use it outside of a component? (I believe there are many others with the same need as me) Could you consider a compromise solution, rather than instructing users on how to avoid the issue?

[hqw567]

In my view, a well-designed library should aim to minimize the cognitive load on developers, enabling them to code more intuitively rather than having them spend a significant amount of time learning how to avoid potential pitfalls. The goal of a library should be to simplify common tasks and make them straightforward, not to force developers to memorize and navigate through a minefield of issues.

[amannn]

I agree. The blog post I've linked to tries to explain just that, how issues that might not be apparent upfront can be avoided automatically by restricting message consumption to components. It might feel limiting in certain cases but ultimately tries to push for robust code that avoids bugs in the first place.