return internal server error (500) on root page (work fine internal page) in production next build but work perfectly in development mode

[torikul00]

Description

I have implemented next-intl with app router (With i18n routing) . its work fine in development mode but when I build the next js for production then its throwing error (Internal server error - 500) ,says (TypeError: Cannot read properties of undefined (reading 'clientModules') . but the internal page (/about,/services) work fine . it just nor working for root page(/) after production

Verifications

• I've verified that the problem I'm experiencing isn't covered in the docs.
• I've searched for similar, existing issues on GitHub and Stack Overflow.
• I've compared my app to a working example to look for differences.

Mandatory reproduction URL

App Router

Reproduction description

Steps to reproduce:

1. Open reproduction
2. Click on …
3. See error: …

Expected behaviour

Its should work as well after build like development

[github-actions]

Thank you for your report!

Unfortunately, the reproduction is missing or incomplete, and as such we cannot investigate this issue. Please add a reproduction to the issue, otherwise it will be closed automatically.

Templates:

• App Router
• Pages Router

Creating a good bug report takes time.

To help us resolve the issue quickly, please simplify the reproduction as much as possible by removing any unnecessary code, files, and dependencies that are not directly related to the problem. The easier it is for us to see the issue, the faster we can help you.

Apart from the reproduction, make sure to include the precise steps on how to reproduce the issue, e.g.:

1. Open reproduction
2. Click on …
3. See error: …

Thank you for your understanding!

FAQ

"I've included a reproduction, what is missing?"

This comment might have been added because your reproduction doesn't point to a destination where the issue can be reproduced. Please make sure that the latest changes were saved in the reproduction and that the link is correct.

[github-actions]

This issue has been automatically closed because it is currently not actionable and has become stale. If the problem persists, please create a new issue.