#Error Code 500 Pages next14

1 messages · Page 1 of 1 (latest)

night crag
#

Im getting an error code 500 on next pages when deploying to vercel but not in development.

here are the logs

⨯ node:internal/modules/esm/module_job:124
this.module.instantiate();
^
Error: request for '@babel/runtime/helpers/esm/extends' is not in cache
at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
at async ModuleJob.run (node:internal/modules/esm/module_job:190:5) {
code: 'ERR_VM_MODULE_LINK_FAILURE',
page: '/'
}
node:internal/modules/esm/module_job:124
this.module.instantiate();
^
Error: request for '@babel/runtime/helpers/esm/extends' is not in cache
at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
at async ModuleJob.run (node:internal/modules/esm/module_job:190:5) {
code: 'ERR_VM_MODULE_LINK_FAILURE',
page: '/'
}
Error: Runtime exited with error: exit status 1
Runtime.ExitError

torpid egretBOT
#

Hi @night crag. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Based on the error logs you've provided, it seems like there's an issue with the '@babel/runtime/helpers/esm/extends' module not being found in the cache during the build process on Vercel. This issue is not occurring in your development environment, which suggests that there might be a discrepancy between your local and production environments.

Here are a few steps you can take to troubleshoot this issue:

  1. Check your dependencies: Ensure that all your dependencies are correctly installed and that the versions match between your local and production environments.

  2. Build your project locally: Before deploying on Vercel, it's recommended to build your project on your local machine first. This can help catch issues specific to your code or your project's dependencies. You can do this by running the command next build in your local console. If the error happens after building locally, it will help you identify the problem. source (https://vercel.com/docs/deployments/troubleshoot-a-build)

  3. Investigate Build logs: You can access the build logs from your Vercel dashboard. These logs provide insight into what happened during the build of a deployment. source (https://vercel.com/docs/deployments/troubleshoot-a-build)

  4. Contact Vercel Support: If you're still unable to resolve the issue, you can contact Vercel Support (https://vercel.com/help) along with the ID on the error page from your deployment. source (https://vercel.com/docs/errors/platform-error-codes)

Remember, it's important to keep your local and production environments as similar as possible to avoid such discrepancies.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: