Replies: 1 comment
-
Hi, I'm also looking for that reply... basically you must |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am working on a project with Next 14 that has a lot of user interactions and reactivity and i have some doubts about how implement nex-intl in the best way.
How i have a lot of client components and all of this need a lot of translated texts, is better to create a
NextIntlClientProvider
for each component and pass only the messages that will be used or due to the high use of the client components in many locations is better encapsule the entire application in aNextIntlClientProvider
and provide all mesages once?I created a HOC to provide the messages for specifc components but i dont know if in terms of performance this is the best solution.
and a example of use:
Beta Was this translation helpful? Give feedback.
All reactions