Production Build Failure - TypeError: (0 , react_jsx_dev_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxDEV) is not a function #1163

Please check that this issue hasn't been reported before.

• I searched previous Bug Reports didn't find any similar reports.

Expected Behavior

While migrating our application from a development to a production environment, we encountered a TypeError: (0 , react_jsx_dev_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxDEV) is not a function error. This issue occurs when the NODE_ENV variable is switched from "development" to "production". . The application operates perfectly in the development environment, but the error appears in the production environment, both locally (on an Ubuntu system) and in a public network on an AWS Ubuntu instance and using Docker Compose.

Current behaviour

After setting NODE_ENV to "production", I expect that the application will successfully build and deploy using Docker Compose. Once deployed, authentication should take place via OAuth provider after entering the client key and secret key. This transition from "development" to "production" is mainly to ensure that the OAuth authentication mechanism is in place and functioning correctly.

Steps to reproduce

After setting NODE_ENV to "production", I expect that the application will successfully build and deploy using Docker Compose. Once deployed, authentication should take place via OAuth provider after entering the client key and secret key. This transition from "development" to "production" is mainly to ensure that the OAuth authentication mechanism is in place and functioning correctly.

Possible solution

If there is an alternate solution to successfully implement and test OAuth authentication in the production environment (without triggering the aforementioned error), that would be welcome too.

Which Operating Systems are you using?

• Android
• iPhone/iPad
• Linux
• macOS
• Windows

Acknowledgements

• My issue title is concise, descriptive, and in title casing.
• I have searched the existing issues to make sure this bug has not been reported yet.
• I am using the latest version of AgentGPT.
• I have provided enough information for the maintainers to reproduce and diagnose the issue.