Internal Server Error with [email protected]
#2214
Comments
|
I'm not able to reproduce it: |
|
And based on your error stacktrace, it's not related to next-i18next |
Hello and thanks for the quick answer! |
|
Like said, I'm not able to reproduce it, so it might be something in your local setup is wrong. Did you try to clone the repo in a fresh directory and try again? or on a different machine? |
|
yes sure, I made a clean installation several times with pruned pnpm store. |
|
did you also try without pnpm, but with npm ? |
|
tried it now |
|
might be a pnpm issue? |
|
It seems so. |
|
+1, I have the same issue as I upgraded Next to 13.5.4 (Node 18, yarn). I get the same error when I access the deployed app on Vercel. Error: Cannot find module 'core-js/modules/es.array.map.js'
Require stack:
- /var/task/node_modules/next-i18next/dist/commonjs/config/createConfig.js
- /var/task/node_modules/next-i18next/dist/commonjs/appWithTranslation.js
- /var/task/node_modules/next-i18next/dist/commonjs/index.js
- /var/task/packages/web/.next/server/pages/_app.js
- /var/task/node_modules/next/dist/server/require.js
- /var/task/node_modules/next/dist/server/next-server.js
- /var/task/packages/web/___next_launcher.cjs
# ...Edit: it does not happen on all pages using i18n, but on some. I may find out the difference between them and keep you posted. |
|
yes, but issue seems is not related to
or simply copy content of |
|
same here I had to rollback to 13.5.3 seems a problem on next side but good to report here as took me a good day of work trying to figure out which package was failing. |
|
Downgrading to [email protected] works. Here is the log: |
|
@meness |
|
Seems to be an upstream issue vercel/next.js#56357 |
|
Same issue when deployed to Vercel. Using v13.5.4, npm and next-i18next |
|
Same issue after upgrading Next to 13.5.4 and deploying to Vercel (issue is not present in local environment). Downgrading to 13.5.3 fixes the deployment. |
|
I'm investigating the same issue, when running inside a docker container on Azure Web Apps. Seems not to be Vercel specific. Stacktrace is same as above it seems. Can share if needed. |
|
Same issue deploying on Railway with next standalone. Error: Cannot find module 'core-js/modules/es.array.map.js'
Require stack:
- /app/node_modules/next-i18next/dist/commonjs/config/createConfig.js
- /app/node_modules/next-i18next/dist/commonjs/appWithTranslation.js
- /app/node_modules/next-i18next/dist/commonjs/index.js
- /app/.next/server/pages/_app.js
- /app/node_modules/next/dist/server/require.js
- /app/node_modules/next/dist/server/next-server.js
- /app/node_modules/next/dist/server/next.js
- /app/server.js
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1028:15)
at /app/node_modules/next/dist/server/require-hook.js:54:36
at Function.Module._load (node:internal/modules/cjs/loader:873:27)
at Module.require (node:internal/modules/cjs/loader:1100:19)
at Module.mod.require (/app/node_modules/next/dist/server/require-hook.js:64:28)
at require (node:internal/modules/cjs/helpers:119:18)
at Object.<anonymous> (/app/node_modules/next-i18next/dist/commonjs/config/createConfig.js:35:1)
at Module._compile (node:internal/modules/cjs/loader:1198:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
at Module.load (node:internal/modules/cjs/loader:1076:32) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/app/node_modules/next-i18next/dist/commonjs/config/createConfig.js',
'/app/node_modules/next-i18next/dist/commonjs/appWithTranslation.js',
'/app/node_modules/next-i18next/dist/commonjs/index.js',
'/app/.next/server/pages/_app.js',
'/app/node_modules/next/dist/server/require.js',
'/app/node_modules/next/dist/server/next-server.js',
'/app/node_modules/next/dist/server/next.js',
'/app/server.js'
]
} |
|
Removing the '^' of the next-version worked for me. |
This worked for me as well |
|
It looks like this might have been fixed in the this PR which is available in (For those “removing the ^”, know that you’re simply pinning next to 13.5.3—downgrading from 13.5.4 has already been highlighted as a workaround for this issue.) |
|
Though the Internal Server Error is resolved, some pages stop hydrating translations. Only happens sometimes, and not on dev. Context looks like it still has all the data, but useTranslation hook doesn't have any langs. Trying to debug further but just mentioning if anyone else hits a similar experience. |
Remove |
|
FWIW: Errors went away for me after updating to 13.5.5. |
🐛 Bug Report
500 Internal Server Error with next.js version 13.5.4 in standalone build.
To Reproduce
pnpm ipnpm buildnode .next/standalone/server.jshttp://localhost:3000/Actual behavior
Error page opened
Terminal error:
Expected behavior
Home page without an error should be opened
Your Environment
The text was updated successfully, but these errors were encountered: