Nextjs: Overusing intl.init() function

[NaifAlqahtani]

Nextjs: Overusing intl.init() function

[cwtuan]

To support multiple languages, create separate intl instances for each language.

const enUSIntl = new ReactIntlUniversal();
const zhCNIntl = new ReactIntlUniversal();
enUSIntl.init({ locales : {...} , currentLocale: "en-US"});
zhCNIntl.init({ locales : {...} , currentLocale: "zh-CN"});

Use the appropriate intl instance to render pages in different languages.

[NaifAlqahtani]

Thanks for the reply!

I am not concerned with supporting multiple languages.

I am more concerned with performance issues of calling the .init() function across ALL components and pages and routes.

Will that affect anything? Or is it okay? In terms of performance of course.

[cwtuan]

You should only init once at server starts

[NaifAlqahtani]

I see. However, as I stated above, for some reason with Nextjs’s nested pages in app directory as well as server and client side components being rendered separately, it causes a lot of errors in loading locale files. My question is, what are the implications and repercussions of calling init function over all components and pages? Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: cwtuan ***@***.***> Sent: Saturday, November 18, 2023 3:41:26 PM To: alibaba/react-intl-universal ***@***.***> Cc: Naif Alqahtani ***@***.***>; Author ***@***.***> Subject: Re: [alibaba/react-intl-universal] Nextjs: Overusing intl.init() function (Issue #241) You should only init once at server starts — Reply to this email directly, view it on GitHub<#241 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMD55LSYQOV4TXWPWDODAPDYFCUHNAVCNFSM6AAAAAA7NYBBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGQ4TQNZUGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[cwtuan]

There is no problem when you call init multiple times. It's just replace the whole locale data object in react-intl-universal.