Aral Roca Gomez

I tried and works fine. It should work with `ja`, we are using PluralRules from EcmaScript:  If is not working fine with `ja`, probably...

@chanphiromsok would be great to know more details about your project. Maybe is something missing like `i18n.js` file. Thanks

@chanphiromsok do you have a monorepo? https://github.com/aralroca/next-translate#13-how-to-use-next-translate-in-a-mono-repo to better understand the problem if you share a repo reproducing the error we will see what happens. Thanks!

Ok thanks @Yedidya10, I'm going to improve the docs!

It's rare this rule because in the server componentes RFC comments about Server hooks 🤔: https://github.com/reactjs/rfcs/blob/main/text/0188-server-components.md#capabilities--constraints-of-server-and-client-components But if can be a problem we can rename it.

`nextTranslate` plugin a part of loading namespaces for each page is using the [`i18n` routing](https://nextjs.org/docs/pages/building-your-application/routing/internationalization) from the Next.js core. Can you try to remove the plugin but adding this i18n...

Can be related with this one? https://github.com/vercel/next.js/issues/48812

@markky21 it was to investigate if is from the plugin internals issue or from Next.js i18n routing (that the plugin also is using). After your feedback and looks a `next-translate-plugin`...

> deploy -> https://nextjs-13-git-next-translate-fixes-markky21.vercel.app/ Ahg.. After check the deployment the dynamic page still in 404 without the plugin isn't it? So then probably is not related with the next-translate-plugin and...

Maybe related with this: https://github.com/vercel/vercel/issues/9827