How great are you
I have now lost the problem that the main data from mysql does not arrive on the site

This worked for me

Next 13.4.19 didn't work for me.
it's give me Aborted (core dumped)

I'm stuck with both issues, one in 13.4 and the other in 13.5.
Guess I have to downgrade to 13.2.

Just to give an update to anyone who comes here, the issue lies with the compiler mixing forward slashes and Posix-style slashes in the pages.js file.

I fixed this by SSH into my EC2 instance, using vim to modify the page.js to change all forward slashes to backslashes and restarting the server. (This is a bad way to fix it, the compiler should automatically detect the system and set the slashes accordingly). As mentioned in a comment below by ericbergh, you have to compile in an actual linux machine (WSL won't work for some reason) in order to have correct paths. I eventually gave up and just dockerized my entire service which automatically setups the build correct.

Previously this issue didn't occur until SWC was added, so I assume the original hardcoded replacement code for slashes in 2 pull requests (one in 2018 and one in 2022) did not move over. (Anyway, the issue lies in that compiling with WSL on a windows machine still packages the production build with the windows version of swc, when it should be using linux's.

@ugursepetci,
Found the reason for the generation of incorrect paths during assembly.
When building the build, you need to fix the generation of directories by replacing 2 backslashes "\" with 1 forward "/".
To do this, you need to make changes to the file: \node_modules\next\dist\build\handle-externals.js
replace string (180):
return commonjs ${localRes.replace(/.*?next[/\\]dist/, "next/dist")};
on
return commonjs ${localRes.replace(/.*?next[/\\]dist/, "next/dist").replace(/\\/g, "/")};

Suitable for versions 13.4.19++ 13.5+

• This is just a fix, but it's better if the developer takes this into account in the Next.JS build

@DarkPromise, thanks for the tip!

this work! on latest 13.5.6.

without change this Next Js 13.5.6 still unable to deploy on ubuntu server with node js,

same error as above happened again.
"Error: Cannot find module 'next/dist\client\components\static-generation-async-storage.external.js'"

I think NextJs might need to fix this, since 13.4.X already got this error.

Thanks very much !

Hello, I have tried building it on ubuntu via WSL, but it still did not work. What did you build it with if its working for yours?

I work at a large corp so I'm not directly responsible for the build pipeline. I know that we are running Ubuntu 20.x and Node 18.18.0 however

Hi, thanks for the reply. I will try it out tomorrow at work. Thanks again.

I fixed mine by compiling within docker instead of locally. If you have that option you can try it.

#56010 (reply in thread)

The solution at above.

It work fine on me at next 13.5.6

local deployment always worked but not on azure with github ci/cd pipeline. i always encountered this error;

Error: Cannot find module '../server/require-hook'

deployment over visual studio code extensions for azure app service worked perfectly!!! thanks!

did you found a solution with github ci/cd though?

Same issue but on AWS. I thought it was PM2's fault.