Dynamic imports causes 404 in production

[paulxuca]

Currently attempting to deploy a next.js to production with dynamic imports (without using next/dynamic since we're importing a non-react library), and running into issues with 404s on the dynamically imported chunks.

The built folder structure looks like:

.next
	- app.js
	- BUILD_ID
	- 0-cd29260af35981b4adfc.js
	- ...etc
	

While loading the page, a javascript file at /_next/webpack/0-cd29260af35981b4adfc.js is loaded, pointing to the file 0-cd29260af35981b4adfc.js to be in the .next/chunks directory, which it's not. Moving that file manually to the chunks folder fixes it. Currently, the request 404s.

• [x ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The request for the dynamically loaded javascript file should not 404.

Current Behavior

The request for the dynamically loaded javascript 404s.

Your Environment

Tech	Version
next	5.0.0
node	8.9.4
OS	MacOs
browser	Chrome
etc

[timneutkens]

Could you provide a reproducible repository 🙏 Then we can look into it 👍

[chilijung]

@paulxuca I also had this problem, dynamic import is working in dev mode but break in production (I could find the output files in .next folder. But loading the wrong path prod files. Have you find a solution for this?

@timneutkens here a repo you could reproduce this issue.: https://github.com/Canner/canner-firebase-cms/tree/nextjs

Where our CMS component dynamic import: https://github.com/Canner/canner/blob/master/src/components/Generator.js#L153-L159

log in to dashboard page, all the CMS components is loading via dynamic import, in dev mode, dynamic import works, but in prod, it breaks it was loading the wrong path.

built file in .next folder looks like this:

Loading 404 files in prod server.

[timneutkens]

Should be fixed by #4639