nextintlClientProvider performance footprint
Unanswered
American black bear posted this in #help-forum
American black bearOP
I was wondering, would it improve the performance if an app with next-itl (without locale routing) uses only the useTranslation hook in server components and passes the translation to client components instead of using nextintlClientProvider to immediately use translations in client components without the need to pass the translations as props?
To me it looks like a tradeoff between using nextintlClientProvider for cleaner code and not using it and having to clutter your components' props with the translation labels.
I'd like to keep using nextintlClientProvider as long as it isn't performance heavy.
Thank you all! 🙂
To me it looks like a tradeoff between using nextintlClientProvider for cleaner code and not using it and having to clutter your components' props with the translation labels.
I'd like to keep using nextintlClientProvider as long as it isn't performance heavy.
Thank you all! 🙂